| 2 | Approval of the agenda | |
|---|---|---|
| R4-2000000 | Agenda for RAN4#94-e | RAN4 Chairman |
| R4-2002162 | Agenda for RAN4#94-e | Futurewei |
| 3 | Letters / reports from other groups / meetings | |
| R4-2000001 | E-meeting arrangements and guidelines | RAN4 Chairman |
| R4-2000002 | RAN4#93 Meeting Report | ETSI MCC |
| R4-2002764 | Reply LS on CSI-RS measurement outside DRX active time | RAN1 |
| R4-2002765 | LS on agreements related to NR Positionin | RAN1 |
| R4-2002766 | LS on XDD-FRX Differentiation | RAN1 |
| R4-2002767 | LS on NR Rel-16 TEI | RAN1 |
| R4-2002768 | Reply LS to RAN1&4 on UE capabilities on DAPS HO | RAN1 |
| R4-2002769 | Reply LS on Tx switching between two uplink carriers | RAN1 |
| R4-2002770 | Reply LS on uplink TDM pattern for LTE DAPS based enhanced make-before-break HO | RAN1 |
| R4-2002771 | Reply LS on sidelink synchronization under multiple synchronization sources with different timing | RAN1 |
| R4-2002772 | LS on Conditional PSCell addition/change | RAN2 |
| R4-2002773 | LS on CLI measurements UE capabilities | RAN2 |
| R4-2002774 | LS on RRM Measurement Relaxation for UE Power Saving in NR | RAN2 |
| R4-2002775 | Reply LS on UL-SL prioritization | RAN2 |
| R4-2002776 | LS on MDT Measurements | RAN2 |
| R4-2002777 | LS on measurement reporting criteria for EN-DC | RAN2 |
| R4-2002778 | LS on secondary DRX group | RAN2 |
| R4-2002779 | LS on inter-RAT HO from SA to EN-DC | RAN2 |
| R4-2002780 | LS on RAN2 progress on SCell uplink behaviour of the UE in dormancy | RAN2 |
| R4-2002781 | LS Response to “Liaison Statement on CCSA progress on NR FR1 OTA” | CTI OTA CA Task Force |
| R4-2002782 | Reply LS on 5G-NR FR2 Transmitter & Receiver Testability Issues | MSG TFES |
| 6 | Rel15 New radio access technology [NR_newRAT] | |
| R4-2000524 | 38.307 CR power class | Nokia, Nokia Shanghai Bell |
| R4-2000557 | 38.307 CR power class REL-15 | Nokia, Nokia Shanghai Bell |
| R4-2002910 | 38.307 CR power class REL-15 | Nokia, Nokia Shanghai Bell |
| 6.1 | Requirements for NE-DC (option 4) and NGEN-DC Maintenance [NR_newRAT-Core] | |
| R4-2002675 | Email discussion summary for RAN4#94e_#1_NR_NewRAT_DC | Moderator (Ericsson) |
| R4-2002874 | Email discussion summary for RAN4#94e_#1_NR_NewRAT_DC | Moderator (Ericsson) |
| 6.1.1 | RF requirements (38.101-3) [NR-newRAT-Core] | |
| R4-2001227 | CR on correction of 38.101-3 NEDC Ppowerclass (Rel-15) | OPPO |
| R4-2001228 | CR on correction of 38.101-3 NEDC Ppowerclass (Rel-16) | OPPO |
| 6.3 | System Parameters Maintenance [NR_newRAT-Core] | |
| R4-2002676 | Email discussion summary for RAN4#94e_ #2_NR_NewRAT_SysParameters | Moderator (ZTE) |
| R4-2002717 | WF on adding 30KHz SCS for n40 SSB | Huawei, HiSilicon |
| R4-2002875 | Email discussion summary for RAN4#94e_ #2_NR_NewRAT_SysParameters | Moderator (ZTE) |
| 6.3.2 | Channel Arrangement Maintenance [NR_newRAT-Core] | |
| R4-2000193 | Add 30KHz SCS for n40 SSB | Huawei, HiSilicon |
| R4-2000194 | TS38.101-1 CR: adding 30KHz SSB SCS for n40 | Huawei, HiSilicon |
| R4-2000195 | TS38.101-1 CR: adding 30KHz SSB SCS for n40 (Rel-16) | Huawei, HiSilicon |
| R4-2000196 | TS38.101-1 CR: adding 30KHz SSB SCS for n40 (Rel-16) | Huawei, HiSilicon |
| R4-2000489 | CR to TS 38.101-3: Correct the intra-band ENDC channel spacing | ZTE Corporation |
| R4-2000490 | CR to TS 38.101-3: Correct the intra-band ENDC channel spacing | ZTE Corporation |
| R4-2001783 | CR for 38.101-1 channel space for CA_Rel15 | Huawei, HiSilicon |
| R4-2001784 | CR for 38.101-1 channel space for CA_Rel16 | Huawei, HiSilicon |
| R4-2001785 | CR for 38.101-2 channel space for CA_Rel15 | Huawei, HiSilicon |
| R4-2001786 | CR for 38.101-2 channel space for CA_Rel16 | Huawei, HiSilicon |
| R4-2002718 | CR to TS 38.101-3: Correct the intra-band ENDC channel spacing | ZTE Corporation |
| 6.3.3 | Other system parameters maintenance [NR_newRAT-Core] | |
| R4-2002144 | FR2 ACLR Measurement Bandwidth Definition | Skyworks Solutions Inc. |
| 6.4 | SUL and LTE-NR co-existence maintenance [NR_newRAT-Core] | |
| R4-2001697 | CR to 38.101-3 R15 to remove FDM ULSUP combinations | Skyworks Solutions Inc. |
| R4-2001716 | CR to 38.101-3 R16 to remove FDM ULSUP combinations | Skyworks Solutions Inc. |
| R4-2002677 | Email discussion summary for RAN4#94e_#3_NR_NewRAT_SUL_LNC | Moderator (Huawei) |
| 6.5 | UE RF requirements maintenance [NR_newRAT] | |
| R4-2000220 | Necessity of signaling supported NS values | NTT DOCOMO, INC. |
| R4-2000221 | Broadening a definition of “modifiedMPR-Behaviour” for 38.101-1 | NTT DOCOMO, INC. |
| R4-2000222 | Broadening a definition of “modifiedMPR-Behaviour” for 38.101-1 | NTT DOCOMO, INC. |
| R4-2000223 | Broadening a definition of “modifiedMPR-Behaviour” for 38.101-2 | NTT DOCOMO, INC. |
| R4-2000224 | Broadening a definition of “modifiedMPR-Behaviour” for 38.101-2 | NTT DOCOMO, INC. |
| R4-2000225 | Broadening a definition of “modifiedMPR-Behaviour” for 38.101-3 | NTT DOCOMO, INC. |
| R4-2000226 | Broadening a definition of “modifiedMPR-Behaviour” for 38.101-3 | NTT DOCOMO, INC. |
| R4-2002678 | Email discussion summary for RAN4#94e_#4_NR_NewRAT_UE_RF | Moderator (Qualcomm) |
| R4-2002726 | WF on Tx EVM for UL MIMO | Qualcomm |
| R4-2002727 | WF on Testability issue with OoBB for FR1 EN-DC UE | Anritsu |
| R4-2002728 | WF on NR UE receiver ACS test requirements | MediaTek |
| R4-2002729 | WF on WRC-19 resolutions | NTT DOCOMO |
| R4-2002733 | WF on Max duty cycle clarifications | Apple |
| R4-2002735 | R15 CR to 38.101-2: TRS and SSB configurations in FR2 | Qualcomm Incorporated |
| R4-2002736 | R16 CR to 38.101-2: TRS and SSB configurations in FR2 | Qualcomm Incorporated |
| R4-2002737 | WF on Signalling supported NS values | NTT DOCOMO |
| R4-2002738 | WF on UL MIMO PC2 | Huawei, HiSilicon |
| R4-2002873 | R15 CR to 38.101-2: TRS and SSB configurations in FR2 | Qualcomm Incorporated |
| R4-2002876 | Email discussion summary for RAN4#94e_#4_NR_NewRAT_UE_RF | Moderator (Qualcomm) |
| R4-2002918 | R15 CR to 38.101-2: TRS and SSB configurations in FR2 | Qualcomm Incorporated |
| 6.5.1.1 | Draft CR for 38.101-1 for editorial errors only [NR_newRAT-Core] | |
| R4-2000119 | CR to 38.101-1 UL MIMO MPR reference table | vivo |
| R4-2000120 | CR to 38.101-1 UL MIMO MPR reference table | vivo |
| R4-2000594 | CR for TS38.101-1, Remove notes for UE channel bandwidth | CATT |
| R4-2000595 | CR for TS38.101-1, Remove notes for UE channel bandwidth | CATT |
| R4-2000596 | CR for TS38.101-1, Correction of IE RF-Parameters name of maxUplinkDutyCycle | CATT |
| R4-2000597 | CR for TS38.101-1, Correction of IE RF-Parameters name of maxUplinkDutyCycle | CATT |
| R4-2000598 | CR for TS38.101-3, Correction of IE RF-Parameters name of maxUplinkDutyCycle | CATT |
| R4-2000743 | CR for TS 38.101-1: Editorial addition of CBW definition in Abbreviations section | MediaTek Inc. |
| R4-2000744 | CR for TS 38.101-1: Editorial addition of CBW definition in Abbreviations section | MediaTek Inc. |
| R4-2002146 | Removal of unnecessary definition of offsetmax,IMD3 from Table 6.2.3.2-1 | Motorola Mobility España SA |
| R4-2002148 | Removal of unnecessary definition of offsetmax,IMD3 from Table 6.2.3.2-1 | Motorola Mobility España SA |
| R4-2002719 | CR for TS38.101-1, Remove notes for UE channel bandwidth | CATT |
| R4-2002909 | Removal of unnecessary definition of offsetmax,IMD3 from Table 6.2.3.2-1 | Motorola Mobility España SA |
| 6.5.1.2 | Draft CR for 38.101-2 for editorial errors only [NR_newRAT-Core] | |
| R4-2000397 | CR to 38.101-2 (Rel-15) MPR for CA | Intel Corporation |
| R4-2000398 | CR to 38.101-2 (Rel-16) MPR for CA | Intel Corporation |
| R4-2000695 | CR to 38.101-2: Align Rx CA requirements structure with TS38.101-1 | Qualcomm Incorporated |
| R4-2000696 | CR to 38.101-2: Align Rx CA requirements structure with TS38.101-1 | Qualcomm Incorporated |
| R4-2000745 | CR for TS 38.101-2: Editorial addition of CBW and CABW definitions in Abbreviations section | MediaTek Inc. |
| R4-2000746 | CR for TS 38.101-2: Editorial addition of CBW and CABW definitions in Abbreviations section | MediaTek Inc. |
| R4-2000912 | CR to TS 38.101-2 Correction on FRC table for FR2 DL 64QAM(R15) | China Telecom |
| R4-2000913 | CR to TS 38.101-2 Correction on FRC table for FR2 DL 64QAM(R16) | China Telecom |
| R4-2002720 | CR to 38.101-2 (Rel-15) MPR for CA | Intel Corporation |
| R4-2002721 | CR for TS 38.101-2: Editorial addition of CBW and CABW definitions in Abbreviations section | MediaTek Inc. |
| R4-2002917 | CR to 38.101-2 (Rel-15) MPR for CA | Intel Corporation |
| 6.5.1.3 | Draft CR for 38.101-3 for editorial errors only [NR_newRAT-Core] | |
| R4-2000453 | CR to TS 38.101-3: editorial corrections on Rx requirements for intra-band contiguous EN-DC | Xiaomi |
| R4-2000454 | CR to TS 38.101-3: editorial corrections on Rx requirements for intra-band contiguous EN-DC | Xiaomi |
| R4-2000892 | CR to TS 38.101-3: editorial correction for output power dynamics for intra-band EN-DC | CHTTL |
| R4-2000893 | CR to TS 38.101-3: editorial correction for output power dynamics for intra-band EN-DC | CHTTL |
| R4-2002098 | EN-DC configuration table corrections | Nokia, Nokia Shanghai Bell |
| R4-2002099 | EN-DC configuration table corrections | Nokia, Nokia Shanghai Bell |
| R4-2002722 | CR to TS 38.101-3: editorial corrections on Rx requirements for intra-band contiguous EN-DC | Xiaomi |
| R4-2002723 | EN-DC configuration table corrections | Nokia, Nokia Shanghai Bell |
| 6.5.2.1 | Maintenance for bands and band combinations for 38.101-1 [NR_newRAT-Core] | |
| R4-2000413 | CR for 38.101-1: n41 and n25 corrections | Sprint Corporation |
| R4-2000414 | Mirror CR for 38.101-1: n41 and n25 corrections | Sprint Corporation |
| R4-2000525 | Correction of NR CA bandwidth classe B and F | Nokia, Nokia Shanghai Bell |
| R4-2001069 | CR for 38.101-1: removing the fallback group for NR CA configuration (Rel-15) | Huawei, HiSilicon |
| R4-2001070 | CR for 38.101-1: removing the fallback group for NR CA configuration (Rel-16) | Huawei, HiSilicon |
| R4-2001308 | Introduction of the Annex modifiedMPR-Behaviour into the NR SA specification | Ericsson |
| R4-2001309 | Introduction of the Annex modifiedMPR-Behaviour into the NR SA specification | Ericsson |
| 6.5.2.2 | Maintenance for combinations for 38.101-2 [NR_newRAT-Core] | |
| R4-2000521 | CR FR2 CA tables REL15 | Nokia, Nokia Shanghai Bell |
| R4-2000523 | CR FR2 CA tables REL16 | Nokia, Nokia Shanghai Bell |
| R4-2000559 | CR to TS 38.101-2 on corrections to intra-band contiguous CA for FR2 bands (Rel-15) | ZTE Corporation |
| R4-2000562 | CR to TS 38.101-2 on corrections to intra-band contiguous CA for FR2 bands (Rel-16) | ZTE Corporation |
| R4-2001310 | Removal of contradicting fall-back specification for intra-band non-contigous CA/DC | Ericsson |
| R4-2001311 | Removal of contradicting fall-back specification for intra-band non-contigous CA/DC | Ericsson |
| R4-2002922 | CR FR2 CA tables REL15 | Nokia, Nokia Shanghai Bell |
| 6.5.2.3 | Maintenance for combinations for 38.101-3 [NR_newRAT-Core] | |
| R4-2000410 | CR for 38.101-3: Correction of MOP tolerance for B41/n41 EN-DC | Sprint Corporation |
| R4-2000411 | Mirror CR for 38.101-3: Correction of MOP tolerance for B41/n41 EN-DC | Sprint Corporation |
| R4-2000854 | CR to introduce new BCS of intra-band continuous EN-DC for TS 38.101-3(Rel-15) | KDDI Corporation |
| R4-2000857 | Cat. A CR to introduce new BCS of intra-band continuous EN-DC for TS 38.101-3(Rel-16) | KDDI Corporation |
| R4-2001312 | Removal of contradicting fall-back specification for intra-band non-contigous CA/DC | Ericsson |
| R4-2001313 | Removal of contradicting fall-back specification for intra-band non-contigous CA/DC | Ericsson |
| R4-2001314 | Removal of the Annex modifiedMPR-Behaviour from the NSA specification | Ericsson |
| R4-2001315 | Removal of the Annex modifiedMPR-Behaviour from the NSA specification | Ericsson |
| R4-2001518 | Rel-15 CR to 38.101-3 for editorial corrections | Ericsson |
| R4-2002118 | CR for [agreed] asynchronous operation for NR CA n78-n79 | NTT DOCOMO INC. |
| R4-2002119 | CR for [agreed] asynchronous operation for NR CA n78-n79 | NTT DOCOMO INC. |
| R4-2002724 | Rel-15 CR to 38.101-3 for editorial corrections | Ericsson |
| 6.5.3 | [FR1] Tx and Rx common [NR_newRAT-Core] | |
| R4-2000491 | CR to TS 38.101-1: Replace CBW with symbols defined in the specification. | ZTE Corporation |
| R4-2000492 | CR to TS 38.101-1: Replace CBW with symbols defined in the specification. | ZTE Corporation |
| R4-2001767 | CR for inter-band CA Tx requirement_Rel-15 | Huawei, HiSilicon |
| R4-2001768 | CR for inter-band CA Tx requirement_Rel-16 | Huawei, HiSilicon |
| R4-2001769 | CR for inter-band ENDC Tx requirement_Rel-15 | Huawei, HiSilicon |
| R4-2001770 | CR for inter-band ENDC Tx requirement_Rel-16 | Huawei, HiSilicon |
| R4-2003083 | CR for inter-band CA Tx requirement_Rel-16 | Huawei, HiSilicon |
| R4-2003084 | CR for inter-band ENDC Tx requirement_Rel-16 | Huawei, HiSilicon |
| 6.5.4.1 | EN-DC power class and UL MIMO clarifications [NR_newRAT-Core] | |
| R4-2000063 | Clarification of Power Class related features | NTT DOCOMO, INC. |
| R4-2000117 | CR to 38.101-1 clarification of MIMO power class in R15 | vivo |
| R4-2000118 | draft LS on clarification of EN-DC power class in R15 | vivo |
| R4-2001229 | Further on UL MIMO PC2 fallback | OPPO |
| R4-2001316 | Correction of transmitter characteristics for UL-MIMO: powerclass 2 and fallback | Ericsson |
| R4-2001317 | Correction of transmitter characteristics for UL-MIMO: powerclass 2 and fallback | Ericsson |
| R4-2002037 | On UL MIMO requirements | Huawei, HiSilicon |
| R4-2002038 | On EN-DC power class | Huawei, HiSilicon |
| R4-2002050 | draft LS on serving cell number for EN-DC power class | Huawei, HiSilicon |
| R4-2002141 | Draft LS on EN-DC power class | Huawei, HiSilicon |
| 6.5.4.2 | UE additional maximum output power reduction (A-MPR) [NR_newRAT-Core] | |
| R4-2000326 | CR to TS 38.101-1 on corrections to network signalling value (Rel-15) | ZTE Corporation |
| R4-2000327 | CR to TS 38.101-1 on corrections to network signalling value (Rel-16) | ZTE Corporation |
| R4-2000400 | CR for 38.101- n39 NS flag change due to conflict | Qualcomm Incorporated |
| R4-2000401 | CR for 38.101- n39 NS flag change due to conflict | Qualcomm Incorporated |
| 6.5.4.3 | Configured transmitted power [NR_newRAT-Core] | |
| R4-2000227 | Avoidance of redundant power reduction for HPUE | NTT DOCOMO, INC. |
| R4-2000228 | Avoidance of redundant power reduction for HPUE for 38.101-1 | NTT DOCOMO, INC. |
| R4-2000229 | Avoidance of redundant power reduction for HPUE for 38.101-1 | NTT DOCOMO, INC. |
| R4-2000455 | Consideration on high power UE fall back enhancement | Xiaomi |
| R4-2002158 | CR for power class fallback enhancement | Huawei, HiSilicon |
| R4-2002725 | Avoidance of redundant power reduction for HPUE | NTT DOCOMO, INC. |
| 6.5.4.5 | Other Tx requirements [NR_newRAT-Core] | |
| R4-2000204 | FR1 TX EVM test condition correction for ULMIMO | Qualcomm Incorporated |
| R4-2000205 | CR to 38.101-1: Revision to ULMIMO EVM spec | Qualcomm Incorporated |
| R4-2000206 | CR to 38.101-1: Revision to ULMIMO EVM spec | Qualcomm Incorporated |
| R4-2000354 | Correction on UL MIMO Emission requirements and alignment with RAN1 terminology | Qualcomm Incorporated |
| R4-2000355 | Correction on UL MIMO Emission requirements and alignment with RAN1 terminology | Qualcomm Incorporated |
| R4-2000356 | Correction on UL MIMO Emission requirements and alignment with RAN1 terminology | Qualcomm Incorporated |
| R4-2000795 | On the condition of antenna configuration for UL-MIMO in FR1 | SoftBank Corp. |
| R4-2000959 | On correction of UE co-ex tables for Japan | SoftBank Corp., NTT docomo INC., KDDI Corporation |
| 6.5.5.2 | Other Rx requirements [NR_newRAT-Core] | |
| R4-2000439 | Testability issue with OoBB for FR1 EN-DC UE | Anritsu Corporation |
| R4-2000440 | CR to out-of-band blocking for DC in FR1 | Anritsu Corporation |
| R4-2000441 | CR to out-of-band blocking for DC in FR1 | Anritsu Corporation |
| R4-2000449 | CR to TS 38.101-1: corrections on ACS for intra-band contiguous CA | Xiaomi |
| R4-2000450 | CR to TS 38.101-1: corrections on ACS for intra-band contiguous CA | Xiaomi |
| R4-2000451 | CR to TS 38.101-3: corrections on ACS for intra-band contiguous EN-DC | Xiaomi |
| R4-2000452 | CR to TS 38.101-3: corrections on ACS for intra-band contiguous EN-DC | Xiaomi |
| R4-2000747 | NR UE receiver ACS test requirements | MediaTek Inc. |
| R4-2000748 | LS on NR UE receiver ACS test requirements | MediaTek Inc. |
| 6.5.6 | [FR2] Common to Tx and Rx [NR_newRAT-Core] | |
| R4-2000198 | CR to 38.101-2 to correct Link and Meas Angles | Keysight Technologies UK Ltd |
| R4-2000200 | On LS from RAN5 on multi-band relaxations | Qualcomm Incorporated |
| R4-2000201 | Reply to LS R5-199424 on FR2 Multiband Relaxations | Qualcomm Incorporated |
| R4-2000202 | CR to 38.101-2: Revision to Multiband Relaxations | Qualcomm Incorporated |
| R4-2000203 | CR to 38.101-2: Revision to Multiband Relaxations | Qualcomm Incorporated |
| R4-2000526 | Discussion on RAN5 LS on Multiband relaxation for FR2 | Nokia, Nokia Shanghai Bell |
| R4-2001780 | clarification on beam lock function for Tx RF requirement measurement | Huawei, HiSilicon |
| R4-2002734 | CR to 38.101-2 to correct Link and Meas Angles | Keysight Technologies UK Ltd |
| 6.5.6.1 | Regulatory Tx/Rx spurious emission limits handling [NR_newRAT-Core] | |
| R4-2000091 | On 3GPP band n258 and WRC-19 EESS unwanted emission limits | T-Mobile USA, AT&T |
| R4-2000212 | CR to 38.101-2: A-MPR Corrections | Qualcomm Incorporated |
| R4-2000213 | CR to 38.101-2: A-MPR Corrections | Qualcomm Incorporated |
| R4-2000214 | Impact of EN 301 908-25 on FR2 | Qualcomm Incorporated |
| R4-2000215 | dCR to 38.101-2: NS extension to n257 | Qualcomm Incorporated |
| R4-2000216 | Impact of WRC19 resolutions on FR2 | Qualcomm Incorporated |
| R4-2000217 | dCR to 38.101-2: Visualizing A-MPR from WRC19 Resolutions | Qualcomm Incorporated |
| R4-2000218 | dCR to 38.101-2: NS extension to n257 | Qualcomm Incorporated |
| R4-2000219 | dCR to 38.101-2: Visualizing A-MPR from WRC19 Resolutions | Qualcomm Incorporated |
| R4-2000409 | On 3GPP band n258 and WRC-19 EESS unwanted emission limits | T-Mobile USA, AT |
| R4-2001775 | On FR2 EESS protection emission requirement | Huawei, HiSilicon |
| 6.5.7.1 | Power control [NR_newRAT-Core] | |
| R4-2000107 | Pcmax correction for CA | Qualcomm Incorporated |
| R4-2000109 | Background for Pcmax correction for CA | Qualcomm Incorporated |
| R4-2000402 | Pcmax correction for CA | Qualcomm Incorporated |
| R4-2001387 | Correction on transmission gap for FR2 relative power tolerance | Ericsson |
| R4-2001388 | Correction on transmission gap for FR2 relative power tolerance | Ericsson |
| R4-2001765 | CR for FR2 CA Pcmax_Rel-15 | Huawei, HiSilicon |
| R4-2001766 | CR for FR2 CA Pcmax_Rel-16 | Huawei, HiSilicon |
| R4-2002730 | Pcmax correction for CA | Qualcomm Incorporated |
| R4-2002731 | Correction on transmission gap for FR2 relative power tolerance | Ericsson |
| 6.5.7.2 | Beam correspondence [NR_newRAT-Core] | |
| R4-2001763 | CR for 38.101-2 side condition for BC_Rel15 | Huawei, HiSilicon |
| R4-2001764 | CR for 38.101-2 side condition for BC_Rel16 | Huawei, HiSilicon |
| R4-2002732 | CR for 38.101-2 side condition for BC_Rel15 | Huawei, HiSilicon |
| 6.5.7.3 | Other Tx requirements [NR_newRAT-Core] | |
| R4-2000003 | Correction of the FR2 RMC slot patterns for MOP test cases | Apple Inc. |
| R4-2000004 | Correction of the FR2 RMC slot patterns for MOP test cases | Apple inc. |
| R4-2000005 | Clarification for the definition of the UL duty cycle | Apple Inc. |
| R4-2000010 | Correction of FR2 64QAM UL RMC | Apple Inc. |
| R4-2000011 | Correction of FR2 64QAM UL RMC | Apple Inc. |
| R4-2000084 | [draft] LS on clarification for the definition of the UL duty cycle | Apple Inc. |
| R4-2000230 | EESS protection from n257 | NTT DOCOMO, INC. |
| R4-2000231 | Correction of EESS protection from n257 | NTT DOCOMO, INC. |
| R4-2000232 | Correction of EESS protection from n257 | NTT DOCOMO, INC. |
| R4-2000507 | CR to 38.101-2 (Rel-15) Configured transmitted power for CA | Intel Corporation |
| R4-2000508 | CR to 38.101-2 (Rel-16) Configured transmitted power for CA | Intel Corporation |
| 6.5.8 | [FR2] Receiver characteristics [NR_newRAT-Core] | |
| R4-2000436 | Condition of IBB blocker location in FR2 | Anritsu Corporation |
| R4-2000437 | Correction to in-band interferer offset definition in FR2 | Anritsu Corporation |
| R4-2000438 | Correction to in-band interferer offset definition in FR2 | Anritsu Corporation |
| R4-2000697 | CR to 38.101-2: Removal of Rx requirement for UE in UL MIMO | Qualcomm Incorporated |
| R4-2000698 | CR to 38.101-2: Removal of Rx requirement for UE in UL MIMO | Qualcomm Incorporated |
| R4-2000749 | CR for TS 38.101-2: Clarifications on transmitter power for recevier requirements | MediaTek Inc. |
| R4-2000752 | CR for TS 38.101-2: Clarifications on transmitter power for recevier requirements | MediaTek Inc. |
| 6.7.1 | General and ad-hoc meeting minutes [NR_newRAT-Core] | |
| R4-2001005 | CR to TS 38.104: Regional requirements | NEC |
| R4-2001006 | CR to TS 38.104: Regional requirements | NEC |
| R4-2001007 | CR to TS 38.141-2: Regional requirements | NEC |
| R4-2001008 | CR to TS 38.141-2: Regional requirements | NEC |
| R4-2002366 | Email discussion summary for RAN4#94e_#75_NR_NewRAT_RF_BS | Moderator (Ericsson) |
| R4-2002466 | Way forward on EESS protection for NR BS operation in Band n257 and n258 | Ericsson |
| R4-2002504 | Email discussion summary for RAN4#94e_#75_NR_NewRAT_RF_BS | Moderator (Ericsson) |
| 6.7.2 | Transmitter characteristics maintenance [NR_newRAT-Core] | |
| R4-2000891 | CR for background on Category B unwanted emission requirement for BS type 2-O | Samsung |
| R4-2001191 | Additional unwanted emission requirements for the EESS protection from band n257 and n258 | NTT DOCOMO, INC. |
| R4-2001241 | CR to TS 37.104 channel spacing R15 | ZTE Corporation |
| R4-2001242 | CR to TS 37.104 channel spacing R16 catA | ZTE Corporation |
| R4-2001243 | CR to TS 37.141 channel spacing R15 | ZTE Corporation |
| R4-2001244 | CR to TS 37.141 channel spacing R16 catA | ZTE Corporation |
| R4-2001245 | CR to TS 38.104 editorial correction R16 catA | ZTE Corporation |
| R4-2001246 | CR to TS 38.104 editorial correction | ZTE Corporation |
| R4-2001247 | CR to TS 38.104 spurious emission for FR2 R16catA | ZTE Corporation |
| R4-2001248 | CR to TS 38.104 spurious emission for FR2 | ZTE Corporation |
| R4-2001249 | CR to TS 38.817-02 out-of-band blocking boundary | ZTE Corporation |
| R4-2001250 | on WRC-19 FR2 emission requirements | ZTE Corporation |
| R4-2001420 | CR to 38.817-02: Measurement uncertainty for FR2 OTA additional spurious emissions requirements | Nokia, Nokia Shanghai Bell |
| R4-2001421 | CR to TS 38.104: Additional OTA transmitter spurious emissions requirements for EESS protection | Nokia, Nokia Shanghai Bell |
| R4-2001422 | CR to TS 38.104: Additional OTA transmitter spurious emissions requirements for EESS protection | Nokia, Nokia Shanghai Bell |
| R4-2001423 | CR to TS 38.141-2: Additional OTA transmitter spurious emissions requirements for EESS protection | Nokia, Nokia Shanghai Bell |
| R4-2001424 | CR to TS 38.141-2: Additional OTA transmitter spurious emissions requirements for EESS protection | Nokia, Nokia Shanghai Bell |
| R4-2001686 | EESS protection for NR BS operation in Band n257 and n258 | Ericsson |
| R4-2002467 | CR for background on Category B unwanted emission requirement for BS type 2-O | Samsung |
| R4-2002469 | CR to TS 37.104 channel spacing R15 | ZTE Corporation |
| R4-2002470 | CR to TS 37.141 channel spacing R15 | ZTE Corporation |
| 6.7.3 | Receiver characteristics maintenance [NR_newRAT-Core] | |
| R4-2000659 | CR to TR 38.817-02: Clarifications and corrections on receiver dynamic range and other requirements | Nokia, Nokia Shanghai Bell |
| R4-2000660 | CR to TR 38.104: Corrections on rated carrier output power symbols | Nokia, Nokia Shanghai Bell |
| R4-2000661 | CR to TR 38.104: Corrections on rated carrier output power symbols | Nokia, Nokia Shanghai Bell |
| R4-2001004 | CR to TR 38.817-02: Clarification on receiver dynamic range requirement | NEC |
| R4-2002468 | CR to TR 38.817-02: Clarifications and corrections on receiver dynamic range and other requirements | Nokia, Nokia Shanghai Bell |
| R4-2002527 | CR to TS 38.104: Corrections on rated carrier output power symbols | Nokia, Nokia Shanghai Bell |
| R4-2002528 | CR to TS 38.104: Corrections on rated carrier output power symbols | Nokia, Nokia Shanghai Bell |
| 6.8.1 | General and ad-hoc meeting minutes [NR_newRAT-Perf] | |
| R4-2002367 | Email discussion summary for RAN4#94e_#76_NR_NewRAT_Conformance_BS_Part_1 | Moderator (FUTUREWEI) |
| R4-2002368 | Email discussion summary for RAN4#94e_#77_NR_NewRAT_Conformance_BS_Part_2 | Moderator (ZTE) |
| R4-2002462 | WF for using Foffset in BS Conformance specifications | Ericssion |
| R4-2002463 | WF for extreme environment testing | Huawei |
| R4-2002505 | Email discussion summary for RAN4#94e_#76_NR_NewRAT_Conformance_BS_Part_1Email discussion summary for RAN4#94e_#76_NR_NewRAT_Conformance_BS_Part_1 | Moderator (FUTUREWEI) |
| R4-2002506 | Email discussion summary for RAN4#94e_#77_NR_NewRAT_Conformance_BS_Part_2 | Moderator (ZTE) |
| 6.8.2.2 | MSR specifications [NR_newRAT-Perf/Core] | |
| R4-2000898 | CR to TS 37.141: Update on Tx transient period definition | CMCC |
| R4-2000899 | CR to TS 37.141: Update on Tx transient period definition | CMCC |
| R4-2001200 | TS 37.141 - Issues with TC applicabilities for CS17 and CS18 | Ericsson |
| R4-2001201 | CR to TS 37.141 Rel-15 - Issues with TC applicabilities CS17 | Ericsson |
| R4-2001202 | CR to TS 37.141 Rel-16 - Issues with TC applicabilities CS17-CS18 | Ericsson |
| R4-2001685 | CR to 38.141-2 on Correction of Receiver Spurious Emissions | Ericsson |
| 6.8.2.3 | NR conformance testing specifications [NR_newRAT-Perf] | |
| R4-2000662 | CR to TR 38.141-1: Corrections on rated carrier output power symbols | Nokia, Nokia Shanghai Bell |
| R4-2000663 | CR to TR 38.141-1: Corrections on rated carrier output power symbols | Nokia, Nokia Shanghai Bell |
| R4-2000664 | CR to TR 38.141-2: Corrections on rated carrier output power symbols and clarifications on procedure for reverberation chamber | Nokia, Nokia Shanghai Bell |
| R4-2000665 | CR to TR 38.141-2: Corrections on rated carrier output power symbols and clarifications on procedure for reverberation chamber | Nokia, Nokia Shanghai Bell |
| R4-2000675 | CR to TR 38.141-1: Corrections on rated carrier output power symbols | Nokia, Nokia Shanghai Bell |
| R4-2000676 | CR to TR 38.141-1: Corrections on rated carrier output power symbols | Nokia, Nokia Shanghai Bell |
| R4-2000677 | CR to TR 38.141-2: Corrections on rated carrier output power symbols | Nokia, Nokia Shanghai Bell |
| R4-2000678 | CR to TR 38.141-2: Corrections on rated carrier output power symbols | Nokia, Nokia Shanghai Bell |
| R4-2001681 | CR to 38.141-1 Corrections to test models, TPDR and modulation quality tests sections | Nokia, Nokia Shanghai Bell |
| R4-2001682 | CR to 38.141-1 Corrections to test models, TPDR and modulation quality tests sections | Nokia, Nokia Shanghai Bell |
| R4-2001683 | CR to 38.141-2 updates for reference to annex F and OFDM symbol TX power | Nokia, Nokia Shanghai Bell |
| R4-2001684 | CR to 38.141-2 updates for reference to annex F and OFDM symbol TX power | Nokia, Nokia Shanghai Bell |
| R4-2001828 | CR to TS 38.141-1: Corrections for the extreme environment testing , Rel-15 | Huawei |
| R4-2001829 | CR to TS 38.141-2: Corrections for the extreme environment testing , Rel-15 | Huawei |
| R4-2001830 | CR to TS 38.141-1: Corrections for the extreme environment testing , Rel-16 | Huawei |
| R4-2001831 | CR to TS 38.141-2: Corrections for the extreme environment testing , Rel-16 | Huawei |
| R4-2001907 | Corrections related to Foffset across specifications | Ericsson |
| R4-2001908 | Alignment of extreme condition testing for BS output power across specifications | Ericsson |
| R4-2001909 | TS 38.141-2: Editorial corrections | Ericsson |
| R4-2001910 | TS 38.141-1: Correction on testing under extreme conditions for BS output powerr | Ericsson |
| R4-2001911 | TS 38.141-1: Correction on testing under extreme conditions for BS output powerr | Ericsson |
| R4-2001912 | TS 38.141-2: Correction on testing under extreme conditions for BS radiated transmit power | Ericsson |
| R4-2001913 | TS 38.141-2: Correction on testing under extreme conditions for BS radiated transmit power | Ericsson |
| R4-2002459 | CR to TR 38.141-1: Corrections on rated carrier output power symbols | Nokia, Nokia Shanghai Bell |
| R4-2002460 | CR to 38.141-2 updates for reference to annex F and OFDM symbol TX power | Nokia, Nokia Shanghai Bell |
| R4-2002461 | TS 38.141-2: Editorial corrections | Ericsson |
| R4-2002529 | CR to TS 38.141-1: Corrections on rated carrier output power symbols | Nokia, Nokia Shanghai Bell |
| R4-2002530 | CR to TS 38.141-2: Corrections on rated carrier output power symbols and clarifications on procedure for reverberation chamber | Nokia, Nokia Shanghai Bell |
| R4-2002531 | CR to TS 38.141-2: Corrections on rated carrier output power symbols and clarifications on procedure for reverberation chamber | Nokia, Nokia Shanghai Bell |
| 6.8.3.1 | Test configurations [NR_newRAT-Perf] | |
| R4-2000666 | CR to TR 38.141-1: Corrections on generation of test configurations | Nokia, Nokia Shanghai Bell |
| R4-2000667 | CR to TR 38.141-1: Corrections on generation of test configurations | Nokia, Nokia Shanghai Bell |
| R4-2000668 | CR to TR 38.141-2: Corrections on generation of test configurations | Nokia, Nokia Shanghai Bell |
| R4-2000669 | CR to TR 38.141-2: Corrections on generation of test configurations | Nokia, Nokia Shanghai Bell |
| R4-2000679 | CR to TR 38.141-1: Corrections on generation of test configurations | Nokia, Nokia Shanghai Bell |
| R4-2000680 | CR to TR 38.141-1: Corrections on generation of test configurations | Nokia, Nokia Shanghai Bell |
| R4-2000681 | CR to TR 38.141-2: Corrections on generation of test configurations | Nokia, Nokia Shanghai Bell |
| R4-2000682 | CR to TR 38.141-2: Corrections on generation of test configurations | Nokia, Nokia Shanghai Bell |
| R4-2002453 | CR to TR 38.141-1: Corrections on generation of test configurations | Nokia, Nokia Shanghai Bell |
| R4-2002532 | CR to TS 38.141-2: Corrections on generation of test configurations | Nokia, Nokia Shanghai Bell |
| 6.8.3.3 | Test models [NR_newRAT-Perf] | |
| R4-2001171 | Discussion on random data content of physical channels for NR test models | CATT |
| R4-2001676 | Discussion on data content for NR test models | Nokia, Nokia Shanghai Bell |
| R4-2001677 | CR to 38.141-1 updates for OSTP calculations | Nokia, Nokia Shanghai Bell |
| R4-2001678 | CR to 38.141-1 updates for OSTP calculations | Nokia, Nokia Shanghai Bell |
| R4-2001679 | CR to 38.141-2 updates for OSTP calculations | Nokia, Nokia Shanghai Bell |
| R4-2001680 | CR to 38.141-2 updates for OSTP calculations | Nokia, Nokia Shanghai Bell |
| R4-2001722 | Random data content of physical channels for NR test modes | Ericsson |
| R4-2001723 | CR to TS 38.141-1: Random data content for NR BS Test Models | Ericsson |
| R4-2001724 | CR to TS 38.141-1: Random data content for NR BS Test Models | Ericsson |
| R4-2001725 | CR to TS 38.141-2: Random data content for NR BS Test Models | Ericsson |
| R4-2001726 | CR to TS 38.141-2: Random data content for NR BS Test Models | Ericsson |
| R4-2001730 | Scrambling and initialization for test models | Futurewei |
| R4-2001805 | Study on NR Test Model signal characteristic by data content choice | Keysight Technologies UK Ltd |
| R4-2002454 | CR to TS 38.141-1: Random data content for NR BS Test ModelsCR | Ericsson |
| R4-2002455 | CR to TS 38.141-2: Random data content for NR BS Test Models | Ericsson |
| R4-2002456 | CR to 38.141-1 updates for OSTP calculations | Nokia, Nokia Shanghai Bell |
| R4-2002457 | CR to 38.141-2 updates for OSTP calculations | Nokia, Nokia Shanghai Bell |
| 6.8.4 | Conducted conformance testing (38.141-1) [NR_newRAT-Perf] | |
| R4-2001824 | CR to TS 38.141-1: OBUE Cat. B Option 2 correction for n7, Rel-15 | Huawei |
| R4-2001825 | CR to TS 38.141-1: OBUE Cat. B Option 2 correction for n7, Rel-16 | Huawei |
| R4-2002458 | CR to TS 38.141-1: OBUE Cat. B Option 2 correction for n7, Rel-15 | Huawei |
| 6.8.5 | Radiated conformance testing (38.141-2) [NR_newRAT-Perf] | |
| R4-2001826 | CR to TS 38.141-2: OBUE Cat. B Option 2 correction for n7 and n38, Rel-15 | Huawei |
| R4-2001827 | CR to TS 38.141-2: OBUE Cat. B Option 2 correction for n7 and n38, Rel-16 | Huawei |
| 6.8.5.1 | Common to FR1 and FR2 radiated conformance testing [NR_newRAT-Perf] | |
| R4-2002042 | Simulation analysis of correlation between wanted and in-band unwanted emissions | Nokia, Nokia Shanghai Bell |
| 6.9 | BS EMC [NR_newRAT-Core] | |
| R4-2002369 | Email discussion summary for RAN4#94e_#78_NR_NewRAT_EMC | Moderator (ZTE) |
| R4-2002507 | Email discussion summary for RAN4#94e_#78_NR_NewRAT_EMC | Moderator (ZTE) |
| 6.9.2.1 | Emission requirements [NR_newRAT-Core] | |
| R4-2001905 | EMC for MSR and AAS BS: Proposal for reduction of test configurations - cont. | Ericsson |
| 6.9.2.2 | Immunity requirements [NR_newRAT-Core] | |
| R4-2001906 | EMC RX immunity: Use of reverberation chamber | Ericsson |
| 6.9.3 | Performance requirements [NR_newRAT-Perf] | |
| R4-2001251 | CR to TS 37.114 Add the transmitter exclusion band for MSR BS(subclause 4.4.1) | ZTE Corporation |
| R4-2001252 | CR to TS 38.113 Add the transmitter exclusion band for NR BS(subclause 4.4.1) | ZTE Corporation |
| R4-2001717 | CR to TS 37.114 Add the transmitter exclusion band for MSR BS(subclause 4.1) | ZTE Corporation |
| R4-2001832 | Proposal of using direct field strength approach to measure unwanted radiated emissions from the enclosure port of BS | Huawei |
| R4-2001833 | CR to TS 38.113: direct field strength measurements for the EMC RE, Rel-15 | Huawei |
| R4-2002450 | CR to TS 38.113 Add the transmitter exclusion band for NR BS(subclause 4.4.1) | ZTE Corporation |
| R4-2002451 | CR to TS 37.114 Add the transmitter exclusion band for MSR BS(subclause 4.1) | ZTE Corporation |
| 6.10 | RRM core maintenance (38.133/36.133) [NR_newRAT-Core] | |
| R4-2002164 | Email discussion summary for RAN4#94e_#41_NR_NewRAT_RRM_Core_Part_1 | Moderator (Huawei, HiSilicon) |
| R4-2002290 | Email discussion summary for RAN4#94e_#41_NR_NewRAT_RRM_Core_Part_1 | Moderator (Huawei, HiSilicon) |
| 6.10.1 | General [NR_newRAT-Core] | |
| R4-2000293 | CR to TS38.133 on correction for L1-RSRP measurement report (Section 9.5.3) | Samsung |
| R4-2000294 | CR to TS38.133 on correction for L1-RSRP measurement report (Section 9.5.3) | Samsung |
| R4-2001329 | On QCL Chain | Nokia, Nokia Shanghai Bell |
| R4-2001335 | Regarding measurements outside active time | Nokia, Nokia Shanghai Bell |
| R4-2002200 | CR to TS 38.133: QCL chain depth restriction | Nokia |
| R4-2002201 | CR to TS 38.133: QCL chain depth restriction | Nokia |
| R4-2002203 | CR to TS38.133 on correction for L1-RSRP measurement report (Section 9.5.3) | Samsung |
| 6.10.2 | Editorial CRs [NR_newRAT-Core] | |
| R4-2000510 | Editorial corrections for 38.133 Core Part R16 (Cat A) | ZTE Corporation |
| R4-2000522 | Editorial corrections for 38.133 Core Part R15 | ZTE Corporation |
| R4-2000580 | Editorial correction for active TCI state switching delay | CATT |
| R4-2000581 | Editorial correction for active TCI state switching delay | CATT |
| R4-2000914 | CR for reference correction on L1-RSRP measurement period (section 9.5.3) | MediaTek inc. |
| R4-2000915 | CR for reference correction on L1-RSRP measurement period (section 9.5.3) | MediaTek inc. |
| 6.10.3 | UE measurement capability (38.133/36.133) [NR_newRAT-Core] | |
| R4-2001259 | Remaining issues on NR reporting criteria | ZTE |
| R4-2001260 | CR to 38.133 NR reporting criteria | ZTE |
| R4-2001261 | CR to 36.133 on NR reporting criteria | ZTE |
| R4-2001262 | CR to 36.133 on NR reporting criteria | ZTE |
| R4-2001270 | Reply LS on measurement reporting criteria for EN-DC | ZTE |
| R4-2001278 | Discussion on measurement reporting criteria for EN-DC | ZTE |
| R4-2001331 | Reporting Criteria discussion | Nokia, Nokia Shanghai Bell |
| R4-2001332 | LS on UE reporting criteria | Nokia, Nokia Shanghai Bell |
| R4-2001333 | Reporting Criteria in 36.133 | Nokia, Nokia Shanghai Bell |
| R4-2001920 | Reporting criteria with NR | Ericsson |
| R4-2001921 | Reporting criteria with NR | Ericsson |
| R4-2001922 | On reporting criteria with NR | Ericsson |
| R4-2001923 | On measurement reporting criteria with EN-DC | Ericsson |
| R4-2001924 | Response LS on measurement reporting criteria for EN-DC | Ericsson |
| R4-2002202 | LS on UE reporting criteria | Nokia, Nokia Shanghai Bell |
| 6.10.4 | RRM measurement and measurement gap (38.133/36.133) [NR_newRAT-Core] | |
| R4-2000028 | CR to correct the reference in clause 9.1.1 in 38.133 R15 | ZTE Corporation |
| R4-2000029 | CR to correct the reference in clause 9.1.1 in 38.133 R16 (Cat A) | ZTE Corporation |
| R4-2001330 | Discussion on SMTC configuration in FR2 | Nokia, Nokia Shanghai Bell |
| R4-2001406 | Requirements on measurements outside gaps for FR2 | Ericsson |
| R4-2001407 | Requirements on measurements outside gaps for FR2 | Ericsson |
| R4-2001408 | Requirements on measurements outside gaps for FR2 | Ericsson |
| R4-2001588 | Correction to inter-RAT measurement on LTE serving carrrier | Huawei, HiSilicon |
| R4-2001589 | Correction to inter-RAT measurement on LTE serving carrrier_r16 | Huawei, HiSilicon |
| R4-2001590 | Correction to inter-RAT measurement on NR serving carrrier | Huawei, HiSilicon |
| R4-2001591 | Correction to inter-RAT measurement on NR serving carrrier_r16 | Huawei, HiSilicon, MediaTek |
| R4-2001606 | Discussion on FR2 measurement outside gap | Huawei, HiSilicon, MediaTek |
| R4-2001607 | CR on FR2 measurement requriements outside gaps R15 | Huawei, HiSilicon, MediaTek |
| R4-2001608 | CR on FR2 measurement requriements outside gaps R16 | Huawei, HiSilicon, MediaTek |
| R4-2001787 | CR on TS38.133 for known cell definition of RRM measurement requirement (Section 9.2.4.3 and 9.3.6.3) | MediaTek inc. |
| R4-2001788 | CR on TS38.133 for known cell definition of RRM measurement requirement (Section 9.2.4.3 and 9.3.6.3) | MediaTek inc. |
| R4-2001789 | CR on TS38.133 for modification of the layer 3 and layer 1 measurement sharing factor when both SSB and RSSI symbol to be measured are considered (Section 9.2.5.1) | MediaTek inc. |
| R4-2001790 | CR on TS38.133 for modification of the layer 3 and layer 1 measurement sharing factor when both SSB and RSSI symbol to be measured are considered (Section 9.2.5.1) | MediaTek inc. |
| R4-2001791 | CR on TS38.133 for modification on number of cells and number of SSB to be measured for FR2 intra-freq. measurement (Section 9.2.3) | MediaTek inc. |
| R4-2001792 | CR on TS38.133 for modification on number of cells and number of SSB to be measured for FR2 intra-freq. measurement (Section 9.2.3) | MediaTek inc. |
| R4-2001925 | NR editorial correction | Ericsson |
| R4-2001926 | NR editorial correction | Ericsson |
| R4-2002204 | CR on TS38.133 for modification of the layer 3 and layer 1 measurement sharing factor when both SSB and RSSI symbol to be measured are considered (Section 9.2.5.1) | MediaTek inc. |
| R4-2002324 | CR on TS38.133 for modification on number of cells and number of SSB to be measured for FR2 intra-freq. measurement (Section 9.2.3) | MediaTek inc. |
| R4-2002325 | Correction to inter-RAT measurement on LTE serving carrrier | Huawei, HiSilicon |
| 6.10.6 | Connected state mobility (38.133/36.133) [NR_newRAT-Core] | |
| R4-2000030 | Discussion on handover requirements | ZTE Corporation |
| R4-2000031 | [CR] handover requirements 38.133 R15 | ZTE Corporation |
| R4-2000032 | [CR] handover requirements 38.133 R16 (Cat A) | ZTE Corporation |
| R4-2000033 | Discussion on RRC procedure delay in RRC release with redirection | ZTE Corporation |
| R4-2000034 | [draft] LS on RRC procedure delay in RRC release with redirection | ZTE Corporation |
| R4-2000511 | Discussion on RRC re-establishment requirement | ZTE Corporation |
| R4-2000512 | CR on RRC re-establishment requirements R15 | ZTE Corporation |
| R4-2000513 | CR on RRC re-establishment requirements R16 (Cat A) | ZTE Corporation |
| R4-2002075 | CR 38.133 (6.1.1) Correction to handover requirements | Ericsson |
| R4-2002076 | CR 38.133 (6.1.1) Correction to handover requirements | Ericsson |
| R4-2002205 | [CR] handover requirements 38.133 R15 | ZTE Corporation |
| R4-2002206 | WF on TRRC_procedure_delay for requirements of RRC release with redirection | ZTE |
| R4-2002286 | [CR] handover requirements 38.133 R16 (Cat A) | ZTE Corporation |
| 6.10.7 | Timing (38.133/36.133) [NR_newRAT-Core] | |
| R4-2002217 | WF on one-shot timing adjustment requirement | Huawei, HiSilicon |
| 6.10.7.1 | One shot timing adjustment requirements [NR_newRAT-Core] | |
| R4-2000458 | UE UL timing adjustment due to Rx beam change | MediaTek inc. |
| R4-2001009 | Discussion on one shot timing adjustment for UE UL timing adjustment | NEC |
| R4-2001258 | Further discussion on one shot timing adjustment requirements | ZTE |
| R4-2001265 | CR to 38.133 on one shot timing adjustment requirements | ZTE |
| R4-2001266 | CR to 38.133 on one shot timing adjustment requirements | ZTE |
| R4-2001328 | One shot UL transmit timing adjustment | Nokia, Nokia Shanghai Bell |
| R4-2001567 | Further discussion on UE one-shot timing adjustment requirements | Huawei, HiSilicon |
| R4-2001568 | CR on removing one-shot timing adjustment requirements | Huawei, HiSilicon |
| R4-2001569 | CR on removing one-shot timing adjustment requirements (Cat A) | Huawei, HiSilicon |
| R4-2001843 | Further analysis of one shot timing adjustment requirements | Ericsson |
| R4-2001844 | Threshold for one shot UE timing adjustment requirements | Ericsson |
| R4-2001845 | Threshold for one shot UE timing adjustment requirements | Ericsson |
| R4-2002062 | Further discussion on UL one shot timing adjustment | Qualcomm Incorporated |
| 6.10.7.2 | MTTD and MRTD requirements [NR_newRAT-Core] | |
| R4-2001570 | CR on inter-band EN-DC and NE-DC synchronous requirements | Huawei, HiSilicon |
| 6.10.8 | Signaling characteristics (38.133/36.133) [NR_newRAT-Core] | |
| R4-2002165 | Email discussion summary for RAN4#94e_#42_NR_NewRAT_RRM_Core_Part_2 | Moderator (Apple) |
| R4-2002291 | Email discussion summary for RAN4#94e_#42_NR_NewRAT_RRM_Core_Part_2 | Moderator (Apple) |
| 6.10.8.1 | RLM [NR_newRAT-Core] | |
| R4-2001584 | Correction on Psharingfactor | Huawei, HiSilicon |
| R4-2001585 | Correction on Psharingfactor_r16 | Huawei, HiSilicon |
| R4-2002207 | Correction on Psharingfactor | Huawei, HiSilicon |
| 6.10.8.2 | SCell activation delay requirements [NR_newRAT-Core] | |
| R4-2002077 | On corrections to SCell activation delay requirements | Ericsson |
| R4-2002078 | CR 38.133 (8.3.2) Corrections to SCell activation delay requirements | Ericsson |
| R4-2002079 | CR 38.133 (8.3.2) Corrections to SCell activation delay requirements | Ericsson |
| R4-2002080 | CR 38.133 (8.3.2) Correction of error in Rel-16 SCell activation | Ericsson |
| R4-2002208 | CR 38.133 (8.3.2) Corrections to SCell activation delay requirements | Ericsson |
| 6.10.8.3 | PSCell addition/release requirements (36.133) [NR_newRAT-Core] | |
| R4-2000055 | [CR] SCell activation delay 38.133 R15 | ZTE Corporation |
| R4-2000056 | [CR] SCell activation delay 38.133 R16 (Cat A) | ZTE Corporation |
| R4-2002081 | On corrections to PSCell change delay requirements | Ericsson |
| R4-2002082 | CR 38.133 (8.11) Corrections to PSCell change delay requirements | Ericsson |
| R4-2002083 | CR 38.133 (8.11) Corrections to PSCell change delay requirements | Ericsson |
| R4-2002209 | [CR] SCell activation delay 38.133 R15 | ZTE Corporation |
| R4-2002210 | CR 38.133 (8.11) Corrections to PSCell change delay requirements | Ericsson |
| R4-2002346 | [CR] SCell activation delay 38.133 R16 (Cat A) | ZTE Corporation |
| 6.10.8.4 | TCI state switching requirements [NR_newRAT-Core] | |
| R4-2000035 | CR for TCI state switch 38.133 R15 | ZTE Corporation |
| R4-2000036 | CR for TCI state switch 38.133 R16 (Cat A) | ZTE Corporation |
| R4-2000514 | Discussion on TCI state known status mismatch | ZTE Corporation |
| R4-2000789 | CR on RAN4 requirement of TCI change for R15 | Apple |
| R4-2000790 | CR on RAN4 requirement of TCI change for R16 | Apple |
| R4-2001010 | Problem of TCI state known status mismatch | NEC |
| R4-2001015 | CR to address TCI state known status mismatch in 38.133 | NEC |
| R4-2001026 | CR on TCI state switch | MediaTek inc. |
| R4-2001334 | Correction to Active TCI state list update delay | Nokia, Nokia Shanghai Bell |
| R4-2001668 | Correction on the MAC based TCI state switching | Huawei, HiSilicon |
| R4-2001669 | Correction on the MAC based TCI state switching | Huawei, HiSilicon |
| R4-2002052 | Corrections to MAC based TCI state switch | Qualcomm Incorporated |
| R4-2002066 | CR for correction to MAC-CE based TCI State switch timeline (Clause 8.10.3) | Qualcomm Incorporated |
| R4-2002067 | CR for correction to MAC-CE based TCI State switch timeline (Clause 8.10.3) | Qualcomm Incorporated |
| R4-2002211 | CR on TCI state switch | MediaTek inc. |
| R4-2002327 | CR on TCI state switch | MediaTek inc. |
| R4-2002339 | CR on TCI state switch | MediaTek inc. |
| 6.10.8.5 | BWP switching requirements [NR_newRAT-Core] | |
| R4-2000906 | Corrections for BWP switch delay R15 | ZTE Corporation |
| R4-2000907 | Corrections for BWP switch delay R16 (Cat A) | ZTE Corporation |
| R4-2001586 | Correction to BWP switching delay | Huawei, HiSilicon |
| R4-2001587 | Correction to BWP switching delay_r16 | Huawei, HiSilicon |
| R4-2002212 | Corrections for BWP switch delay R15 | ZTE Corporation |
| R4-2002213 | Correction to BWP switching delay | Huawei, HiSilicon |
| R4-2002347 | Corrections for BWP switch delay R16 (Cat A) | ZTE Corporation |
| 6.10.9 | Beam management based on SSB and/or CSI-RS (38.133) [NR_newRAT-Core] | |
| R4-2000916 | CR for measurement restriction in FR2 across CCs (section 8.1.2.3, 8.1.3.3, 8.5.2.3, 8.5.3.3, 8.5.5.3, 8.5.6.3, 9.5.5.1, 9.5.5.2) | MediaTek inc. |
| R4-2000917 | CR for measurement restriction in FR2 across CCs (section 8.1.2.3, 8.1.3.3, 8.5.2.3, 8.5.3.3, 8.5.5.3, 8.5.6.3, 9.5.5.1, 9.5.5.2) | MediaTek inc. |
| R4-2000918 | CR for SSB based candidate beam detection (section 8.5.5.2) | MediaTek inc. |
| R4-2000919 | CR for SSB based candidate beam detection (section 8.5.5.2) | MediaTek inc. |
| R4-2000920 | CR for CSI-RS based L1-RSRP measurement period (section 9.5.4.2) | MediaTek inc. |
| R4-2000921 | CR for CSI-RS based L1-RSRP measurement period (section 9.5.4.2) | MediaTek inc. |
| R4-2000922 | CR on TSMTCperiod (section 8.1.2.2, 8.1.3.2, 8.5.2.2, 8.5.3.2, 8.5.5.2, 8.5.6.2, 9.5.4.1, 9.5.4.2) | MediaTek inc., Huawei, HiSilicon |
| R4-2000923 | CR on TSMTCperiod (section 8.1.2.2, 8.1.3.2, 8.5.2.2, 8.5.3.2, 8.5.5.2, 8.5.6.2, 9.5.4.1, 9.5.4.2) | MediaTek inc., Huawei, HiSilicon |
| 6.10.10 | Requirements for NE-DC (option 4) and NGEN-DC [NR_newRAT-Core] | |
| R4-2001609 | CR to remove RSTD requirements for NE-DC in 36.133 R15 | Huawei, HiSilicon |
| R4-2001610 | CR to remove RSTD requirements for NE-DC in 36.133 R16 | Huawei, HiSilicon |
| 6.10.12 | Other requirements [NR_newRAT-Core] | |
| R4-2000026 | CR to correct the header of Table for OTDOA 38.133 R15 | ZTE Corporation |
| R4-2000027 | CR to correct the header of Table for OTDOA 38.133 R16 (Cat A) | ZTE Corporation |
| 6.11 | RRM perf maintenance (38.133/36.133) [NR_newRAT-Perf] | |
| R4-2002166 | Email discussion summary for RAN4#94e_#43_NR_NewRAT_RRM_Perf_Part_1 | Moderator (Ericsson) |
| R4-2002167 | Email discussion summary for RAN4#94e_#44_NR_NewRAT_RRM_Perf_Part_2 | Moderator (Huawei, HiSilicon) |
| R4-2002292 | Email discussion summary for RAN4#94e_#43_NR_NewRAT_RRM_Perf_Part_1 | Moderator (Ericsson) |
| R4-2002293 | Email discussion summary for RAN4#94e_#44_NR_NewRAT_RRM_Perf_Part_2 | Moderator (Huawei, HiSilicon) |
| 6.11.1 | General [NR_newRAT-Perf] | |
| R4-2000037 | CR to remove duplicated units in tables in clause 10.1 | ZTE Corporation |
| R4-2000038 | CR to remove duplicated units in tables in clause 10.1 (Cat A) | ZTE Corporation |
| R4-2001592 | Correction to configurations for TRS | Huawei, HiSilicon |
| R4-2001593 | Correction to configurations for TRS_r16 | Huawei, HiSilicon |
| R4-2001619 | OCNG pattern for TDM-ed SSB R15 | Huawei, HiSilicon |
| R4-2001620 | OCNG pattern for TDM-ed SSB R16 | Huawei, HiSilicon |
| R4-2002214 | Correction to configurations for TRS | Huawei, HiSilicon |
| 6.11.2 | Editorial CRs [NR_newRAT-Perf] | |
| R4-2000515 | Editorial corrections for 38.133 Perf Part R15 | ZTE Corporation |
| R4-2000516 | Editorial corrections for 38.133 Perf Part R16 (Cat A) | ZTE Corporation |
| R4-2001223 | Editorial corrections to make test cases appear in Table of contents | ANRITSU LTD |
| R4-2001225 | Editorial corrections to make test cases appear in Table of contents | ANRITSU LTD |
| R4-2001365 | CR to TS 38.133: Corrections to FR1-FR2 event triggered test cases Annex A.5 (Rel-15) | Rohde & Schwarz |
| R4-2001366 | CR to TS 38.133: Corrections to FR1-FR2 event triggered test cases Annex A.5 (Rel-16) | Rohde & Schwarz |
| R4-2001367 | CR to TS 38.133: Corrections to FR1-FR2 event triggered test cases Annex A.7 (Rel-15) | Rohde & Schwarz |
| R4-2001368 | CR to TS 38.133: Corrections to FR1-FR2 event triggered test cases Annex A.7 (Rel-16) | Rohde & Schwarz |
| R4-2001369 | CR to TS 38.133: Clarifications to AoA setup and AoA cell assignement Annex A.5 (Rel-15) | Rohde & Schwarz |
| R4-2001370 | CR to TS 38.133: Clarifications to AoA setup and AoA cell assignement Annex A.5 (Rel-16) | Rohde & Schwarz |
| R4-2001371 | CR to TS 38.133: Clarifications to AoA setup Annex A.8 (Rel-15) | Rohde & Schwarz |
| R4-2001372 | CR to TS 38.133: Clarifications to AoA setup Annex A.8 (Rel-16) | Rohde & Schwarz |
| R4-2002215 | Editorial corrections for 38.133 Perf Part R15 | ZTE Corporation |
| R4-2002330 | Editorial corrections for 38.133 Perf Part R16 (Cat A) | ZTE Corporation |
| 6.11.3 | RRM test cases [NR_newRAT-Perf] | |
| R4-2001600 | Correction to RF channels configuration | Huawei, HiSilicon |
| R4-2001601 | Correction to RF channels configuration_r16 | Huawei, HiSilicon |
| 6.11.3.1 | RRC_IDLE state mobility test cases [NR_newRAT-Perf] | |
| R4-2000082 | Corrections to RRM Test case A.7.1.1.2 | ANRITSU LTD |
| R4-2000083 | Corrections to RRM Test case A.7.1.1.2 | ANRITSU LTD |
| R4-2000163 | Correction to FR1-E-UTRA Inter-RAT cell re-selection test cases | ANRITSU LTD |
| R4-2000164 | Correction to FR1-E-UTRA Inter-RAT cell re-selection test cases | ANRITSU LTD |
| 6.11.3.1.1 | SA idle/inactive cell reselection [NR_newRAT-Perf] | |
| R4-2001617 | CR on cell reselection test cases for FR2 SA R15 | Huawei, HiSilicon |
| R4-2001618 | CR on cell reselection test cases for FR2 SA R16 | Huawei, HiSilicon |
| 6.11.3.2.4 | Random access [NR_newRAT-Perf] | |
| R4-2001611 | CR on random access test case R15 | Huawei, HiSilicon |
| R4-2001612 | CR on random access test case R16 | Huawei, HiSilicon |
| 6.11.3.2.5 | RRC Release with redirection to NR/E-UTRAN [NR_newRAT-Perf] | |
| R4-2001602 | Correction to RRC release with redirection TCs | Huawei, HiSilicon |
| R4-2001603 | Correction to RRC release with redirection TCs_r16 | Huawei, HiSilicon |
| 6.11.3.3 | Timing test cases [NR_newRAT-Perf] | |
| R4-2000168 | Correction to SRS periodicity and Offset for UL transit timing with DRx config | ANRITSU LTD |
| R4-2000169 | Correction to SRS periodicity and Offset for UL transit timing with DRx config | ANRITSU LTD |
| 6.11.3.4 | RLM test cases [NR_newRAT-Perf] | |
| R4-2002135 | PRACH configurations in FR1 SSB based RLM tests | Qualcomm |
| R4-2002160 | PRACH configurations in FR1 SSB based RLM tests | Qualcomm |
| R4-2002227 | PRACH configurations in FR1 SSB based RLM tests | Qualcomm |
| R4-2002331 | PRACH configurations in FR1 SSB based RLM tests | Qualcomm |
| R4-2002332 | PRACH configurations in FR1 SSB based RLM tests | Qualcomm |
| 6.11.3.4.1 | EN-DC SSB RLM for PSCell IS and OOS [NR_newRAT-Perf] | |
| R4-2001613 | CR on SSB RLM test cases EN-DC R15 | Huawei, HiSilicon |
| R4-2001614 | CR on SSB RLM test cases EN-DC R16 | Huawei, HiSilicon |
| 6.11.3.4.2 | SA SSB RLM for PCell IS and OOS [NR_newRAT-Perf] | |
| R4-2001615 | CR on SSB RLM test cases SA R15 | Huawei, HiSilicon |
| R4-2001616 | CR on SSB RLM test cases SA R16 | Huawei, HiSilicon |
| 6.11.3.5 | Interruption test cases [NR_newRAT-Perf] | |
| R4-2001596 | Correction to interruption TCs | Huawei, HiSilicon |
| R4-2001597 | Correction to interruption TCs_r16 | Huawei, HiSilicon |
| 6.11.3.7 | UE UL carrier RRC reconfiguration delay test cases [NR_newRAT-Perf] | |
| R4-2001604 | Correction to UL reconfiguration delay TCs | Huawei, HiSilicon |
| R4-2001605 | Correction to UL reconfiguration delay TCs_r16 | Huawei, HiSilicon |
| 6.11.3.8 | Beam failure detection and link recovery procedure test cases [NR_newRAT-Perf] | |
| R4-2002134 | PRACH configurations in FR1 SSB based BFR tests | Qualcomm |
| R4-2002333 | PRACH configurations in FR1 SSB based BFR tests | Qualcomm |
| R4-2002334 | PRACH configurations in FR1 SSB based BFR tests | Qualcomm |
| 6.11.3.10 | Measurement procedure test cases [NR_newRAT-Perf] | |
| R4-2000161 | Correction to Active UL BWP for SA intra-frequency event triggered reporting with per-UE gaps | ANRITSU LTD |
| R4-2000162 | Correction to Active UL BWP for SA intra-frequency event triggered reporting with per-UE gaps | ANRITSU LTD |
| R4-2000166 | Removal of Time offset between PCell and PSCell in SA RRM Test cases | ANRITSU LTD |
| R4-2000167 | Removal of Time offset between PCell and PSCell in SA RRM Test cases | ANRITSU LTD |
| 6.11.3.10.2 | SA cell search and L1 measurement period [NR_newRAT-Perf] | |
| R4-2001598 | Correction to intra-frequency measurement with gap TCs | Huawei, HiSilicon |
| 6.11.3.10.5 | SA NR inter-frequency measurement [NR_newRAT-Perf] | |
| R4-2000382 | CR on test cases for SA FR2 inter-frequency measurement R15 (section A.7.6.2) | Intel Corporation |
| R4-2000383 | CR on test cases for SA FR2 inter-frequency measurement R16 (section A.7.6.2) | Intel Corporation |
| R4-2001599 | Correction to intra-frequency measurement with gap TCs_r16 | Intel Corporation |
| R4-2002216 | CR on test cases for SA FR2 inter-frequency measurement R15 (section A.7.6.2) | Intel Corporation |
| R4-2002340 | CR on test cases for SA FR2 inter-frequency measurement R15 (section A.7.6.2) | Intel Corporation |
| R4-2002341 | CR on test cases for SA FR2 inter-frequency measurement R16 (section A.7.6.2) | Intel Corporation |
| 6.11.3.10.7 | Inter-RAT E-UTRA measurement (with NR PCell) [NR_newRAT-Perf] | |
| R4-2001594 | Correction to FR1 SA inter-RAT measurement TCs | Huawei, HiSilicon |
| R4-2001595 | Correction to FR1 SA inter-RAT measurement TCs_r16 | Huawei, HiSilicon |
| 6.11.3.11.1 | Intra-frequency RSRP accuracy for FR1 and FR2 [NR_newRAT-Perf] | |
| R4-2000170 | Update of Test Requirements, FR2 Intra-frequency SS-RSRP accuracy Test cases | ANRITSU LTD |
| R4-2000171 | Update of Test Requirements, FR2 Intra-frequency SS-RSRP accuracy Test cases | ANRITSU LTD |
| 6.11.3.11.2 | Inter-frequency RSRP accuracy for FR1 and FR2 [NR_newRAT-Perf] | |
| R4-2000172 | Update of Test requirements, FR2 Inter-frequency SS-RSRP accuracy Test cases | ANRITSU LTD |
| R4-2000173 | Update of Test requirements, FR2 Inter-frequency SS-RSRP accuracy Test cases | ANRITSU LTD |
| 6.11.3.11.4 | Inter-frequency RSRQ accuracy for FR1 and FR2 [NR_newRAT-Perf] | |
| R4-2001373 | CR to TS 38.133: Addition of TC A.4.7.2.2 (Rel-15) | Rohde & Schwarz |
| R4-2001374 | CR to TS 38.133: Addition of TC A.4.7.2.2 (Rel-16) | Rohde & Schwarz |
| R4-2001565 | CR on test case in A.4.7.2.2 | Huawei, HiSilicon |
| R4-2001566 | CR on test case in A.4.7.2.2 (Cat A) | Huawei, HiSilicon |
| 6.11.3.11.6 | Beam management: L1-RSRP reporting [NR_newRAT-Perf] | |
| R4-2001396 | Editorial correction of EN-DC FR1 L1-RSRP measurement for beam reporting | Ericsson |
| R4-2001397 | Editorial correction of EN-DC FR1 L1-RSRP measurement for beam reporting | Ericsson |
| R4-2001398 | Editorial correction of NR SA FR1 L1-RSRP measurement for beam reporting | Ericsson |
| R4-2001399 | Editorial correction of NR SA FR1 L1-RSRP measurement for beam reporting | Ericsson |
| 6.12 | Demodulation and CSI maintenance [NR_newRAT-Perf] | |
| R4-2002380 | Email discussion summary for RAN4#94e_#89_NR_NewRAT_Demod | Moderator (Intel) |
| R4-2002445 | Way forward on HARQ timing for NR BS demodulation conformance testing | Huawei |
| R4-2002518 | Email discussion summary for RAN4#94e_#89_NR_NewRAT_Demod | Moderator (Intel) |
| R4-2002534 | Way forward on DL Channels mapping and power ratio | Intel |
| 6.12.1 | UE demodulation and CSI (38.101-4) [NR_newRAT-Perf] | |
| R4-2000076 | Clarification of Random PMI when testing | ANRITSU LTD |
| R4-2000081 | Correction to 5.3.3 4Rx PDCCH Demod Requirements | ANRITSU LTD |
| R4-2000353 | CR on corrections for FR1 PDSCH demodulation performance tests | Qualcomm Incorporated |
| R4-2000358 | CR to TS 38.101-4: Editorial corrections (R15) | Intel Corporation |
| R4-2000564 | On signal power ratios and mapping for UE requirements | Rohde & Schwarz |
| R4-2000565 | Update of DL physical channels | Rohde |
| R4-2001002 | CR on number of NZP CSI-RS ports for RI reporting test in a TDD 4Rx test case | MediaTek inc. |
| R4-2001450 | CR: Updates to NR PDSCH test parameters (Rel-15) | Huawei, HiSilicon |
| R4-2002446 | Clarification of Random PMI when testing | ANRITSU LTD |
| R4-2002447 | Correction to 5.3.3 4Rx PDCCH Demod Requirements | ANRITSU LTD |
| R4-2002448 | CR on corrections for FR1 PDSCH demodulation performance tests | Qualcomm Incorporated |
| R4-2002449 | CR to TS 38.101-4: Editorial corrections (R15) | Intel Corporation |
| 6.12.2 | BS demodulation (38.104) [NR_newRAT-Perf] | |
| R4-2000295 | CR on correction of NR UCI on PUSCH conducted performance requirements for TS 38.141-1 | Samsung |
| R4-2000296 | CR on correction of NR UCI on PUSCH conducted performance requirements for TS 38.141-1 | Samsung |
| R4-2000297 | CR on correction of NR UCI on PUSCH radiated performance requirements for TS 38.141-2 | Samsung |
| R4-2000298 | CR on correction of NR UCI on PUSCH radiated performance requirements for TS 38.141-2 | Samsung |
| R4-2001172 | IntraSlot frequency hopping applicability in the one OFDM symbol test case | Ericsson |
| R4-2001173 | IntraSlot frequency hopping applicability in the one OFDM symbol test case | Ericsson |
| R4-2001174 | IntraSlot frequency hopping applicability in the one OFDM symbol test case | Ericsson |
| R4-2001175 | IntraSlot frequency hopping applicability in the one OFDM symbol test case | Ericsson |
| R4-2001176 | IntraSlot frequency hopping applicability in the one OFDM symbol test case | Ericsson |
| R4-2001177 | IntraSlot frequency hopping applicability in the one OFDM symbol test case | Ericsson |
| R4-2001451 | Discussion on HARQ timing for NR BS performance requirements | Huawei, HiSilicon |
| 6.13 | Maintenance of the Positioning specs (36.171, 37.171 and 38.171) [NR_newRAT-Perf or TEI] | |
| R4-2000147 | Update of the Note 1 in the Power level and satellite allocation table for the Sensitivity Coarse time assistance requirements | Spirent Communications |
| R4-2000148 | Update of the Note 1 in the Power level and satellite allocation table for the Sensitivity Coarse time assistance requirements | Spirent Communications |
| R4-2000149 | Editorial change to TS 37.571-1 title | Spirent Communications |
| R4-2000150 | Editorial change to TS 37.571-1 title | Spirent Communications |
| R4-2000151 | Editorial change to TS 37.571-1 title | Spirent Communications |
| R4-2002168 | Email discussion summary for RAN4#94e_#45_NR_NewRAT_Positioning | Moderator (Spirent Communications) |
| R4-2002218 | Update of the Note 1 in the Power level and satellite allocation table for the Sensitivity Coarse time assistance requirements | Spirent Communications |
| R4-2002219 | Update of the Note 1 in the Power level and satellite allocation table for the Sensitivity Coarse time assistance requirements | Spirent Communications |
| R4-2002294 | Email discussion summary for RAN4#94e_#45_NR_NewRAT_Positioning | Moderator (Spirent Communications) |
| 7.1 | LTE intra-band Carrier Aggregation for x CC DL/y CC UL including contiguous and non-contiguous spectrum (x>=y) [LTE_CA_R16_intra] | |
| R4-2002679 | Email discussion summary for RAN4#94e_#5_LTE_Baskets | Moderator (Ericsson) |
| 7.1.1 | Rapporteur Input (WID/TR/CR) [LTE_CA_R16_intra-Core/Perf] | |
| R4-2001498 | Revised WID Basket WI for LTE Intra-band CA Rel-16 | Ericsson |
| R4-2001505 | TP for TR 36.716-01-01 for updated scope from RAN #86 | Ericsson |
| R4-2001509 | CR introduction of Rel-16 LTE Intra-band combinations in 36.101 | Ericsson |
| 7.1.2 | UE RF [LTE_CA_R16_intra-Core] | |
| R4-2000192 | TP for Rel-16 Intra-band CA for x CC DL/ y CC UL including contiguous and non-contiguous spectrum (x>=y): Bandwidth combination set, REFSENS and insertion loss parameters for CA_48B, CA_48A-48B, CA_48B-48B, CA_48B-48C, CA_48B-48D, CA_48B-48E with 1UL and | Charter Communications |
| R4-2002568 | TP for Rel-16 Intra-band CA for x CC DL/ y CC UL including contiguous and non-contiguous spectrum (x>=y): Bandwidth combination set, REFSENS and insertion loss parameters for CA_48B, CA_48A-48B, CA_48B-48B, CA_48B-48C, CA_48B-48D, CA_48B-48E with 1UL and | Charter Communications |
| 7.2.1 | Rapporteur Input (WID/TR/CR) [LTE_CA_R16_2BDL_1BUL-Core/Perf] | |
| R4-2001375 | Revised WID: Rel16 LTE inter-band CA for 2 bands DL with 1 band UL | Qualcomm Incorporated |
| R4-2001376 | Introduction of Rel-16 LTE inter-band CA for 2 bands DL with 1 band UL combinations in TS36101 | Qualcomm Incorporated |
| 7.2.3 | UE RF without specific issues [LTE_CA_R16_2BDL_1BUL-Core] | |
| R4-2000175 | TP to TR 36.716-02-01: CA_2-26 | Nokia, Nokia Shanghai Bell |
| R4-2000176 | TP to TR 36.716-02-01: CA_26-66 | Nokia, Nokia Shanghai Bell |
| R4-2001377 | Draft CR for 2DL/1UL CA_2-48 | Qualcomm Incorporated, Verizon |
| R4-2001378 | Draft CR for 2DL/1UL CA_2-66 | Qualcomm Incorporated, Verizon |
| R4-2001379 | Draft CR for 2DL/1UL CA_4-5 | Qualcomm Incorporated, Verizon |
| R4-2001380 | Draft CR for 2DL/1UL CA_5-66 | Qualcomm Incorporated, Verizon |
| R4-2001381 | Draft CR for 2DL/1UL CA_13-46 | Qualcomm Incorporated, Verizon |
| R4-2002564 | TP to TR 36.716-02-01: CA_2-26 | Nokia, Nokia Shanghai Bell |
| R4-2002565 | TP to TR 36.716-02-01: CA_26-66 | Nokia, Nokia Shanghai Bell |
| 7.3.1 | Rapporteur Input (WID/TR/CR) [LTE_CA_R16_3BDL_1BUL-Core/Perf] | |
| R4-2001778 | Introduction of completed R16 3DL band combinations to TS 36.101 | Huawei, HiSilicon |
| R4-2001782 | Revised WID for LTE inter-band CA for 3 bands DL with 1 bands UL | Huawei, HiSilicon |
| 7.3.2 | UE RF with harmonic, close proximity and isolation issues [LTE_CA_R16_3BDL_1BUL-Core] | |
| R4-2002006 | draft CR 36.101 to add missing fallback CA_1A-1A-3A-3A-7A | Ericsson, Telstra |
| 7.3.3 | UE RF without specific issues [LTE_CA_R16_3BDL_1BUL-Core] | |
| R4-2000177 | TP to TR 36.716-03-01: CA_2-7-26 | Nokia, Nokia Shanghai Bell |
| R4-2000178 | TP to TR 36.716-03-01: CA_2-26-66 | Nokia, Nokia Shanghai Bell |
| R4-2000179 | TP to TR 36.716-03-01: CA_7-26-66 | Nokia, Nokia Shanghai Bell |
| R4-2000486 | TP for TR 36.716-03-01: CA_1-20-38 | ZTE Corporation |
| R4-2002566 | TP to TR 36.716-03-01: CA_2-7-26 | Nokia, Nokia Shanghai Bell |
| R4-2002567 | TP to TR 36.716-03-01: CA_2-26-66 | Nokia, Nokia Shanghai Bell |
| R4-2002569 | TP for TR 36.716-03-01: CA_1-20-38 | ZTE Corporation |
| R4-2002633 | TP to TR 36.716-03-01: CA_7-26-66 | Nokia, Nokia Shanghai Bell |
| 7.4.1 | Rapporteur Input (WID/TR/CR) [LTE_CA_R16_xBDL_1BUL-Core] | |
| R4-2000174 | Introduction of LTE inter-band Carrier Aggregation for x bands DL (x=4, 5) with 1 band UL to TS36.101 | Nokia, Nokia Shanghai Bell |
| R4-2000329 | Revised WI: Rel'16 LTE inter-band CA for x bands DL (x=4, 5) with 1 band UL | Nokia, Nokia Shanghai Bell |
| R4-2000330 | TR 36.716-04-01 v0.8.0 | Nokia, Nokia Shanghai Bell |
| R4-2000331 | Updated scope of TR: Rel'16 LTE inter-band CA for x bands DL (x=4, 5) with 1 band UL | Nokia, Nokia Shanghai Bell |
| 7.4.2 | UE RF with 4 LTE bands CA [LTE_CA_R16_xBDL_1BUL-Core] | |
| R4-2000180 | TP to TR 36.716-04-01: CA_2-7-26-66 | Nokia, Nokia Shanghai Bell |
| R4-2000187 | TP to TR 36.716-04-01: Correction of BCS for CA_1A-3C-7A-28A | Nokia, Nokia Shanghai Bell |
| R4-2000188 | TP to TR 36.716-04-01: Correction of BCS for CA_2A-7A-7A-29A-66A | Nokia, Nokia Shanghai Bell |
| R4-2002634 | TP to TR 36.716-04-01: CA_2-7-26-66 | Nokia, Nokia Shanghai Bell |
| 7.5.1 | Rapporteur Input (WID/TR/CR) [LTE_CA_R16_2BDL_2BUL-Core] | |
| R4-2002027 | Revised WID for LTE inter-band CA for 2 bands DL with 2 bands UL | Huawei, HiSilicon |
| 7.6.1 | Rapporteur Input (WID/TR/CR) [LTE_CA_R16_xBDL_2BUL-Core] | |
| R4-2001040 | TR 36.716-03-02 v0.9.0 update: LTE-A x bands DL (x=3,4,5) with 2 bands UL inter-band CA in Rel-16 | LG Electronics France |
| R4-2001041 | Revised WID on LTE-A inter-band CA for x bands (x=3,4,5) DL with 2 bands UL in Rel-16 | LG Electronics France |
| R4-2001169 | Introduction of LTE-A inter-band CA for x bands (x=3,4,5) DL with 2 bands UL into TS36.101 | LG Electronics France |
| 7.6.2 | UE RF with MSD [LTE_CA_R16_xBDL_2BUL-Core] | |
| R4-2001237 | TP on summary of self-interference analysis for new x bands (x=3,4,5) DL with 2 bands UL | LG Electronics Finland |
| R4-2001238 | MSD results for new LTE-A CA band combinations in rel-16 | LG Electronics Finland |
| 7.10.1 | General [LTE_eMTC5] | |
| R4-2000726 | On RRM performance aspects of R16 MTC | Qualcomm Incorporated |
| R4-2001751 | Discussions on performance requirements for Rel-16 MTC | Ericsson |
| R4-2002680 | Email discussion summary for RAN4#94e_#6_LTE_eMTC5 | Moderator (Ericsson) |
| R4-2002741 | WF on remaining issue on TR 37.823 | Ericsson |
| R4-2002877 | Email discussion summary for RAN4#94e_#6_LTE_eMTC5 | Moderator (Ericsson) |
| 7.10.2 | Coexistence with NR [LTE_eMTC5] | |
| R4-2001127 | TP for TR 37.823: Specific aspects for TDD | Huawei Technologies R4-202165D UK |
| R4-2001862 | TR 37.823 LTE-M coexisting with NR v 0.2.0 | Ericsson |
| R4-2001863 | TP for TR 37.823 : R16 RAN1 impact on co-existing | Ericsson |
| R4-2001864 | R16 RAN1 impact on co-existing | Ericsson |
| R4-2002739 | TP for TR 37.823: Specific aspects for TDD | Huawei Technologies R4-202165D UK |
| R4-2002740 | TP for TR 37.823 : R16 RAN1 impact on co-existing | Ericsson |
| 7.10.3 | RRM core requirements (36.133) [LTE_eMTC5-Core] | |
| R4-2002193 | Email discussion summary for RAN4#94e_#70_LTE_eMTC5_RRM | Moderator (Ericsson) |
| R4-2002268 | WF on Rel-16 MTC RRM | Ericsson |
| R4-2002295 | Email discussion summary for RAN4#94e_#70_LTE_eMTC5_RRM | Moderator (Ericsson) |
| 7.10.3.1 | DL quality report in MSG3 and connected mode [LTE_eMTC5-Core] | |
| R4-2001349 | Discussion on the remaining issues on DL quality report for eMTC | Ericsson |
| R4-2001649 | Discussion on quality reporting in Rel-16 eMTC | Huawei, HiSilicon |
| R4-2001650 | CR on MPDCCH parameters for quality reporting | Huawei, HiSilicon |
| 7.10.3.2 | WUS [LTE_eMTC5-Core] | |
| R4-2001651 | CR to introduce WUS reception requirements for Rel-16 eMTC | Huawei, HiSilicon |
| R4-2001750 | Introduction of Rel-16 WUS reception requirements for cat-M1/M2 | Ericsson |
| 7.10.3.3 | MPDCCH performance improvement [LTE_eMTC5-Core] | |
| R4-2000727 | Simulation results for MPDCCH performance improvements of RLM tests in MTC | Qualcomm Incorporated |
| R4-2001350 | Discussion on RLM with MPDCCH improvement | Ericsson |
| 7.10.3.4 | PUR [LTE_eMTC5-Core] | |
| R4-2001652 | CR on measurement requriements for RSRP change based TA validation | Huawei, HiSilicon |
| R4-2001748 | Introduction of requirements for preconfigured uplink resource transmission for cat-M1/M2 | Ericsson |
| R4-2001749 | Support for RSS based CE level selection in RA | Ericsson |
| R4-2002267 | Support for RSS based CE level selection in RA | Ericsson |
| 7.10.3.5 | Mobility enhancement [LTE_eMTC5-Core] | |
| R4-2000728 | On RSS-based measurement in connected mode in eMTC | Qualcomm Incorporated |
| R4-2001653 | Discussion on remaining issues in RSS measurement | Huawei, HiSilicon |
| R4-2001746 | RSS based measurement simulation results and discussions | Ericsson |
| R4-2001747 | CR: RSS based measurement simulation results and discussions | Ericsson |
| R4-2002266 | CR: RSS based measurement simulation results and discussions | Ericsson |
| 7.10.4 | Demodulation and CSI requirements (36.101/36.104) [LTE_eMTC5-Perf] | |
| R4-2000311 | View on BS demodulation requirement for LTE additional enhancement for eMTC | Samsung |
| R4-2001351 | Open issues on UE/BS demodulation requirements for Rel-16 eMTC | Ericsson |
| R4-2001352 | Discussion on UE demodulation and CSI reporting requirements for Rel-16 BL/CE UE | Ericsson |
| R4-2001479 | Discussion on BS performance requirements for additional MTC enhancements for LTE | Huawei, HiSilicon |
| R4-2001480 | Discussion on UE performance requirements for additional MTC enhancements for LTE | Huawei, HiSilicon |
| R4-2001481 | Discussion on initial simulation assumption for MPDCCH of LTE eMTC | Huawei, HiSilicon |
| R4-2001482 | Discussion on initial simulation assumption for CSI reporting of LTE eMTC | Huawei, HiSilicon |
| R4-2001915 | UE and BS demodulation requirements for LTE_eMTC5 | Nokia, Nokia Shanghai Bell |
| R4-2002376 | Email discussion summary for RAN4#94e_#85_LTE_eMTC5_Demod | Moderator (Ericsson) |
| R4-2002426 | Way forward on UE/BS demodulation performance for additional MTC enhancements for LTE | Ericsson |
| R4-2002514 | Email discussion summary for RAN4#94e_#85_LTE_eMTC5_Demod | Moderator (Ericsson) |
| 7.11.1 | General [NB_IOTenh3] | |
| R4-2000729 | On RRM performance aspects of R16 NB-IoT | Qualcomm Incorporated |
| R4-2002681 | Email discussion summary for RAN4#94e_#7_LTE_IOTenh3 | Moderator (Huawei) |
| R4-2002878 | Email discussion summary for RAN4#94e_#7_LTE_IOTenh3 | Moderator (Huawei) |
| 7.11.2 | Co-existence with NR [NB_IOTenh3] | |
| R4-2000670 | TP to TR 37.824: Update of NR TDD UE specific dedicated configuration | Nokia, Nokia Shanghai Bell, ZTE |
| R4-2000671 | CR to TS 38.104: Corrections on NB-IoT operation in NR channel bandwidth | Nokia, Nokia Shanghai Bell |
| R4-2000672 | CR to TS 38.141-1: Introduction of NB-IoT operation in NR channel bandwidth | Nokia, Nokia Shanghai Bell |
| R4-2000683 | TP to TR 37.824: Update of NR TDD UE specific dedicated configuration | Nokia, Nokia Shanghai Bell, ZTE |
| R4-2000684 | CR to TS 38.104: Corrections on NB-IoT operation in NR channel bandwidth | Nokia, Nokia Shanghai Bell |
| R4-2000685 | CR to TS 38.141-1: Introduction of NB-IoT operation in NR channel bandwidth | Nokia, Nokia Shanghai Bell |
| R4-2000699 | Draft TR 37.824 v040 Coexistence between NB-IoT and NR | Futurewei |
| R4-2000700 | TP editorial corrections in TR 37.824 | Futurewei |
| R4-2000816 | Test Configuration for TS 38.141 | Huawei, HiSilicon |
| R4-2000817 | Test Configuration for TS 37.141 | Huawei, HiSilicon |
| R4-2000875 | TP to TR 37.824: modifications for section 5.3 NB-IoT operating in NR guard-band | CHTTL, T-mobile USA, Dish |
| R4-2000970 | Introduction of NB-IoT into TS37.141 | ZTE Corporation |
| R4-2002742 | TP editorial corrections in TR 37.824 | Futurewei |
| R4-2002743 | CR to TS 38.141-1: Introduction of NB-IoT operation in NR channel bandwidth | Nokia, Nokia Shanghai Bell |
| R4-2002744 | Introduction of NB-IoT into TS37.141 | ZTE Corporation |
| R4-2002915 | TP editorial corrections in TR 37.824 | Futurewei |
| 7.11.3 | RRM core requirements (36.133) [NB_IOTenh3-Core] | |
| R4-2002194 | Email discussion summary for RAN4#94e_#71_NB_IOTenh3_RRM | Moderator (Huawei, HiSilicon) |
| R4-2002269 | WF on RRM requirements of R16 enhancement for NB-IoT | Huawei |
| R4-2002296 | Email discussion summary for RAN4#94e_#71_NB_IOTenh3_RRM | Moderator (Huawei, HiSilicon) |
| R4-2002337 | WF on RRM requirements of R16 enhancement for NB-IoT | Huawei |
| 7.11.3.2 | PUR [NB_IOTenh3-Core] | |
| R4-2001550 | CR on measurement requriements for RSRP change based TA validation | Huawei, HiSilicon |
| R4-2002270 | CR on measurement requriements for RSRP change based TA validation | Huawei, HiSilicon |
| 7.11.3.3 | Multi-carrier operations [NB_IOTenh3-Core] | |
| R4-2000730 | Remaining issues on RRM measurements in non-anchor carrier for NB-IoT | Qualcomm Incorporated |
| R4-2001551 | CR on non-anchor RRM measurement requirements in Rel-16 NB IoT | Huawei, HiSilicon |
| R4-2001552 | Discussion on the non-anchor RRM measurement requirements Rel-16 NB IoT | Huawei, HiSilicon |
| R4-2001752 | Remaining discussions on non-anchor carrier RRM measurements | Ericsson |
| R4-2001917 | On NRSRP processing in multicarrier operation | Nokia, Nokia Shanghai Bell |
| R4-2002271 | CR on non-anchor RRM measurement requirements in Rel-16 NB IoT | Huawei, HiSilicon |
| 7.11.3.4 | Others [NB_IOTenh3-Core] | |
| R4-2001553 | Discussion on the TA offset setting for NR and NB-IoT coexistence | Huawei, HiSilicon |
| 7.11.4 | Demodulation and CSI requirements (36.101/36.104) [NB_IOTenh3-Perf] | |
| R4-2000312 | View on BS demodulation requirement for LTE additional enhancement for NB IoT | Samsung |
| R4-2001353 | Open issues on UE/BS demodulation requirements for Rel-16 NB-IoT | Ericsson |
| R4-2001461 | Discussion on NPDSCH performance requirements for additional enhancements for NB-IOT | Huawei, HiSilicon |
| R4-2001462 | Discussion on NPUSCH performance requirements for additional enhancements for NB-IOT | Huawei, HiSilicon |
| R4-2001916 | UE and BS demodulation requirements for NB_IOTenh3 | Nokia, Nokia Shanghai Bell |
| R4-2002377 | Email discussion summary for RAN4#94e_#86_ NB_IOTenh3_Demod | Moderator (Huawei) |
| R4-2002425 | Way forward on LTE UE and BS performance requirements for additional enhancements for NB-IOT | Huawei |
| R4-2002515 | Email discussion summary for RAN4#94e_#86_ NB_IOTenh3_Demod | Moderator (Huawei) |
| 7.12.1 | RRM core requirements (36.133) [LTE_feMob-Core] | |
| R4-2002195 | Email discussion summary for RAN4#94e_#72_LTE_feMob_RRM | Moderator (Nokia) |
| R4-2002272 | WF on LTE feMob RRM requirements | Nokia |
| R4-2002297 | Email discussion summary for RAN4#94e_#72_LTE_feMob_RRM | Moderator (Nokia) |
| 7.12.1.1 | Conditional handover [LTE_feMob-Core] | |
| R4-2001336 | Conditional handover for LTE | Nokia, Nokia Shanghai Bell |
| R4-2001411 | Open issues for NR conditional handover | Ericsson |
| R4-2001412 | TP:Update to conditional handover requirements for LTE | Ericsson |
| R4-2001839 | Correction to HO delay requirements for conditional HO | Qualcomm Incorporated |
| 7.12.1.2 | Reduction of user data interruption [LTE_feMob-Core] | |
| R4-2001409 | Remaining open issues on DAPS handover for LTE | Ericsson |
| R4-2001410 | TP:Update to DAPS handover requirements for LTE | Ericsson |
| R4-2001670 | CR on DAPS handover | Huawei, HiSilicon |
| R4-2001840 | Corrections to LTE DAPS HO requirements | Qualcomm Incorporated |
| 7.13 | Further performance enhancement for LTE in high speed scenario [LTE_high_speed_enh2] | |
| R4-2002378 | Email discussion summary for RAN4#94e_#87_LTE_high_speed_enh2_Demod | Moderator (NTT DoCoMo) |
| R4-2002516 | Email discussion summary for RAN4#94e_#87_LTE_high_speed_enh2_Demod | Moderator (NTT DoCoMo) |
| 7.13.1 | RRM core requirements maintenance (36.133) [LTE_high_speed_enh2-Core] | |
| R4-2000641 | CR on correction of measurement delay requirements for LTE HST in TS36.133 | vivo |
| R4-2000873 | CR to TS 36.133: Finalization on RRM requirements for Rel-16 LTE HST | NTT DOCOMO, INC. |
| R4-2002196 | Email discussion summary for RAN4#94e_#73_LTE_high_speed_enh2_RRM | Moderator (NTT DOCOMO) |
| R4-2002273 | CR on correction of measurement delay requirements for LTE HST in TS36.133 | vivo |
| R4-2002298 | Email discussion summary for RAN4#94e_#73_LTE_high_speed_enh2_RRM | Moderator (NTT DOCOMO) |
| R4-2002345 | CR on correction of measurement delay requirements for LTE HST in TS36.133 | vivo |
| 7.13.3 | UE Demodulation and CSI requirements (36.101) [LTE_high_speed_enh2-Perf] | |
| R4-2000872 | CR to TS 36.101: Finalization on PDSCH demodulation with 500km/h velocity | NTT DOCOMO, INC. |
| 7.13.3.1 | Extension of demodulation requirements to CA [LTE_high_speed_enh2-Perf] | |
| R4-2001348 | Finalization of CA PDSCH demodulation requirements with HST-SFN | Ericsson |
| R4-2002424 | Finalization of CA PDSCH demodulation requirements with HST-SFN | Ericsson |
| 7.13.4 | BS Demodulation requirements (36.104) LTE_high_speed_enh2-Perf] | |
| R4-2002499 | CR to TS 36.104 Updates of PUSCH performance requirements for enhanced HST scenario | NTT DoCoMo |
| R4-2002500 | CR to TS 36.141 Updates of PUSCH performance requirements for enhanced HST scenario | NTT DoCoMo |
| R4-2002501 | CR to TS 36.104 Updates of PRACH performance requirements for enhanced HST scenario | NTT DoCoMo |
| R4-2002502 | CR to TS 36.141 Updates of PRACH performance requirements for enhanced HST scenario | NTT DoCoMo |
| 7.13.4.1 | PUSCH demodulation requirements [LTE_high_speed_enh2-Perf] | |
| R4-2000309 | Simulation results summary of BS demodulation requirement for LTE Rel-16 HST | Samsung |
| R4-2000310 | Simulation results for HST PUSCH in LTE Rel-16 | Samsung |
| R4-2001452 | Simulation results for LTE HST BS demodulation requirements | Huawei, HiSilicon |
| R4-2001720 | Discussion on aligning simulation results of PUSCH for Rel-16 LTE HST | Nokia, Nokia Shanghai Bell |
| 7.13.4.2 | PRACH requirements [LTE_high_speed_enh2-Perf] | |
| R4-2001718 | Discussion on aligning simulation results of PRACH preamble restricted set type B for Rel-16 LTE HST | Nokia, Nokia Shanghai Bell |
| 7.14.3 | Demodulation and CSI requirements (36.101) [LTE_terr_bcast -Perf] | |
| R4-2000773 | On LTE-based 5G terrestrial broadcast demod requirement | Qualcomm, Inc. |
| R4-2001453 | Discussion on the performance requirement for LTE-based 5G terrestrial broadcast | Huawei, HiSilicon |
| R4-2002379 | Email discussion summary for RAN4#94e_#88_LTE_terr_bcast_Demod | Moderator (Qualcomm) |
| R4-2002423 | WF for 5G broadcast demod requirement | Moderator (Qualcomm) |
| R4-2002517 | Email discussion summary for RAN4#94e_#88_LTE_terr_bcast_Demod | Moderator (Qualcomm) |
| R4-2002540 | Email discussion summary for RAN4#94e_#88_LTE_terr_bcast_Demod | Moderator (Qualcomm) |
| 7.15 | Support for NavIC Navigation Satellite System for LTE [LCS_NAVIC-Perf] | |
| R4-2000071 | CR of TS 36.171 for introducing NavIC in LTE – performance part | Reliance Jio, CEWiT, Huawei, ISRO, Saankhya Labs Private Limited, Tejas Networks Ltd. |
| R4-2002197 | Email discussion summary for RAN4#94e_#74_LCS_NAVIC_RRM | Moderator (Reliance Jio) |
| R4-2002274 | CR of TS 36.171 for introducing NavIC in LTE – performance part | Reliance Jio, CEWiT, Huawei, ISRO, Saankhya Labs Private Limited, Tejas Networks Ltd. |
| R4-2002299 | Email discussion summary for RAN4#94e_#74_LCS_NAVIC_RRM | Moderator (Reliance Jio) |
| 7.16 | DL MIMO efficiency enhancements for LTE [LTE_DL_MIMO_EE] | |
| R4-2002039 | On new SRS requirements for LTE eMIMO | Huawei, HiSilicon |
| R4-2002040 | CR for TS 36.101-1 Introduction of new SRS requirements for LTE eMIMO | Huawei, HiSilicon |
| R4-2002682 | Email discussion summary for RAN4#94e_#8_LTE_DL_MIMO_EE | Moderator (Huawei, HiSilicon) |
| R4-2002745 | CR for TS 36.101-1 Introduction of new SRS requirements for LTE eMIMO | Huawei, HiSilicon |
| 8.1.1 | System Parameters [NR_unlic-Core] | |
| R4-2002683 | Email discussion summary for RAN4#94e_#9_NR_unlic_SysParameters | Moderator (Ericsson) |
| R4-2002746 | WF on wideband operation | ZTE |
| R4-2002748 | WF on new intra-band CA BW classes for NR-U | Ericsson |
| R4-2002749 | draftCR to 38.104 on NR-U sync raster | FUTUREWEI |
| R4-2002750 | draftCR to 38.101-1 on NR-U sync raster | FUTUREWEI |
| R4-2002751 | draftCR to 38.104 on NR-U SEM | Nokia |
| R4-2002752 | draftCR to 38.101-1 on NR-U SEM | Nokia |
| R4-2002879 | Email discussion summary for RAN4#94e_#9_NR_unlic_SysParameters | Moderator (Ericsson) |
| R4-2002919 | WF on wideband operation | ZTE |
| 8.1.1.1 | General [NR_unlic-Core ] | |
| R4-2001318 | Additional NR CA bandwidth classes and specification of CA carrier spacing for NR-U | Ericsson |
| R4-2001958 | draftCR to 38.104 on introduction of band n46 | Ericsson |
| R4-2001959 | draftCR to 38.101-1 on introduction of band n46 | Ericsson |
| R4-2002747 | draftCR to 38.101-1 on introduction of band n46 | Ericsson |
| 8.1.1.2 | Wideband operations (UE and BS) [NR_unlic-Core] | |
| R4-2000709 | [NRU] Wideband Operation Back-off Measurements for UE | Skyworks Solutions Inc. |
| R4-2000818 | Further consideration on guard band on wideband operation | Huawei, HiSilicon |
| R4-2000819 | Further consideration on unwanted emission mask for NR-U | Huawei, HiSilicon |
| R4-2000981 | Further discussion on intra-carrier guardband | ZTE Corporation |
| R4-2001306 | NR-U - Capturing the Spectral Emission Mask | Nokia, Nokia Shanghai Bell |
| R4-2001319 | The NR-U channel raster and allowed intra-cell GB for wideband operation | Ericsson |
| R4-2001320 | Nominal intra-cell guard bands for wideband operation | Ericsson |
| R4-2001732 | NR-U Guard band analysis | Futurewei |
| 8.1.1.4 | Spectrum utilizations [NR_unlic-Core] | |
| R4-2000820 | Draft CR to 38.104 on NR-U Spectrum Utilization | Huawei, HiSilicon |
| R4-2000967 | NR-U Spectral Utilization and Wideband Operation | Qualcomm Incorporated |
| 8.1.1.5 | Sync raster [NR_unlic-Core] | |
| R4-2001731 | Sync raster design for NR-U | Futurewei |
| 8.1.2 | UE RF requirements [NR_unlic-Core] | |
| R4-2000190 | [DC] TP for DC_n48-n46 | Charter Communications |
| R4-2000191 | TP for CA_n48-n46 | Charter Communications |
| R4-2001222 | Harmonic MSD discussion for DC_2_n46, CA_n25_n46 | MediaTek Inc., Ericsson |
| R4-2001712 | Standalone NR-U combinations in Rel-16 | Ericsson |
| R4-2001713 | Draft CR on Introduction of standalone NR-U combinations in Rel-16 | Ericsson |
| R4-2001714 | TP on Inclusion of NR-U standalone combinations in TR 38 716-01-01: | Ericsson |
| R4-2002019 | TP to include CA_n25A-n46A | Ericsson, T-Mobile US, MediaTek |
| R4-2002020 | TP to include CA_n46A-n66A | Ericsson, T-Mobile US, MediaTek |
| R4-2002021 | TP to include DC_2A_n46A | Ericsson, T-Mobile US, MediaTek |
| R4-2002022 | TP to include DC_66A_n46A | Ericsson, T-Mobile US, MediaTek |
| R4-2002023 | CR 38.101-1 to include NR CA NR-U combinations | Ericsson |
| R4-2002024 | CR 38.101-3 to include EN-DC NR-U combinations | Ericsson |
| R4-2002684 | Email discussion summary for RAN4#94e_#10_NR_unlic_UE_RF | Moderator (Qualcomm) |
| R4-2002753 | WF on remaining UE Tx requirements for NR-U | Qualcomm |
| R4-2002754 | WF on enabling PC3 for NR-U in Rel-16 | Charter |
| R4-2002755 | WF on additional spurious emission requirements in Band n46 | Nokia |
| R4-2002756 | WF on UE receiver requirements for NR-U | Ericsson |
| R4-2002757 | WF on method and assumptions in determining NR-U MPR and A-MPR in Band n46 | Skyworks |
| R4-2002880 | Email discussion summary for RAN4#94e_#10_NR_unlic_UE_RF | Moderator (Qualcomm) |
| 8.1.2.1 | Transmitter characteristics [NR_unlic-Core] | |
| R4-2000399 | On NR-U ACLR requirement | Intel Corporation |
| R4-2000708 | [NRU] Single Carrier Back-off measurements for UE power class and MPR | Skyworks Solutions Inc. |
| R4-2001321 | Initial simualtions of required MPR and A-MPR for 5 GHz NR-U | Ericsson |
| R4-2002094 | NR-U MPR for PC5 single carrier | Qualcomm Incorporated |
| R4-2002095 | NR-U general and Band n46 specific Tx requirements | Qualcomm Incorporated |
| 8.1.2.2 | Receiver characteristics [NR_unlic-Core] | |
| R4-2002092 | Band n46 reference sensitivity | Qualcomm Incorporated |
| R4-2002093 | NR-U receiver ACS and blocking | Qualcomm Incorporated |
| 8.1.3 | BS RF requirements [NR_unlic-Core] | |
| R4-2000985 | CR for NR-U RX requirement | ZTE Corporation |
| R4-2002370 | Email discussion summary for RAN4#94e_#79_NR_unlic_RF_BS | Moderator (Nokia) |
| R4-2002465 | WF for NR-U FRCs | Nokia |
| R4-2002508 | Email discussion summary for RAN4#94e_#79_NR_unlic_RF_BS | Moderator (Nokia) |
| 8.1.3.2 | Receiver characteristics [NR_unlic-Core] | |
| R4-2000821 | NR-U BS REFSENS | Huawei, HiSilicon |
| R4-2000822 | NR-U BS dynamic range | Huawei, HiSilicon |
| R4-2000982 | simulation results for NR-U BS RX FRC | ZTE Corporation |
| R4-2000983 | NR-U BS RX REFSENS and dynamic range requirement | ZTE Corporation |
| R4-2000984 | NR-U BS RX ICS requirement | ZTE Corporation |
| R4-2001463 | Discussion and simulation results for NR-U BS REFSENS/ICS | Huawei, HiSilicon |
| R4-2001464 | Discussion and simulation results for NR-U BS Dynamic range | Huawei, HiSilicon |
| R4-2001465 | Discussion on FRC definition for NR-U BS REFSENS and Dynamic range | Huawei, HiSilicon |
| R4-2001674 | NR-U BS receiver requirements | Nokia, Nokia Shanghai Bell |
| R4-2001675 | Summary of simulation results for NR-U BS Rx FRC | Nokia, Nokia Shanghai Bell |
| R4-2001727 | Update to NR-U FRC definition | Ericsson, Nokia, Nokia Shanghai Bell |
| R4-2001728 | NR-U BS RX Simulation Results | Ericsson |
| 8.1.4 | RRM core requirements (38.133) [NR_unlic-Core] | |
| R4-2000039 | CR for spec structure to address NR-U in 38.133 v2 | ZTE Corporation |
| R4-2000040 | Discussion on approaches to address NR-U in 36.133 and 38.133 v2 | ZTE Corporation |
| R4-2002169 | Email discussion summary for RAN4#94e_#46_NR_unlic_RRM_Core_Part_1 | Moderator (Ericsson) |
| R4-2002170 | Email discussion summary for RAN4#94e_#47_NR_unlic_RRM_Core_Part_2 | Moderator (MediaTek) |
| R4-2002171 | Email discussion summary for RAN4#94e_#48_NR_unlic_RRM_Core_Part_3 | Moderator (Nokia) |
| R4-2002278 | WF on NR-U RRM requirements (Part 3) | Nokia |
| R4-2002281 | WF on SIB reading in cell reselection and HO requirements for NR-U | Intel |
| R4-2002282 | LS to RAN2 on UL LBT failure recovery for the target cell | RAN4 |
| R4-2002283 | WF on NR-U RRM requirements (Part 1) | Ericsson |
| R4-2002284 | WF on NR-U RRM requirements (Part 2) | MediaTek |
| R4-2002300 | Email discussion summary for RAN4#94e_#46_NR_unlic_RRM_Core_Part_1 | Moderator (Ericsson) |
| R4-2002301 | Email discussion summary for RAN4#94e_#47_NR_unlic_RRM_Core_Part_2 | Moderator (MediaTek) |
| R4-2002302 | Email discussion summary for RAN4#94e_#48_NR_unlic_RRM_Core_Part_3 | Moderator (Nokia) |
| R4-2002335 | WF on NR-U RRM requirements (Part 2) | MediaTek |
| R4-2002336 | WF on NR-U RRM requirements (Part 1) | Ericsson |
| 8.1.4.1 | Cell re-selection [NR_unlic-Core] | |
| R4-2000392 | Discussion on SIB reading impacts on cell reselection requirements of NR-U | Intel Corporation |
| R4-2000714 | Remaining issues on cell reselection in NR-U | Qualcomm Incorporated |
| R4-2000924 | Discussion on cell reselection requirement for NR-U | MediaTek inc. |
| R4-2000925 | Simulation results for SI reading | MediaTek inc. |
| R4-2001438 | On Cell-reselection requirements in NR-U | Nokia, Nokia Shanghai Bell |
| R4-2001554 | Discussion on cell re-selection for NR-U | Huawei, HiSilicon |
| R4-2001741 | Remaining discussions on IDLE mode cell re-selection requirements for NR-U standalone | Ericsson |
| R4-2001742 | Draft CR: NR-U requirements for IDLE/INACTIVE states | Ericsson |
| R4-2001743 | NR-U inter-RAT requirements for IDLE/INACTIVE states | Ericsson |
| R4-2001744 | Remaining discussions on serving cell evaluations for NR-U standalone | Ericsson |
| R4-2001745 | Discussions on paging interruptions for NR-U | Ericsson |
| R4-2001914 | NR-U inter-RAT requirements for IDLE/INACTIVE states | Ericsson |
| 8.1.4.2 | Handover [NR_unlic-Core] | |
| R4-2000393 | Further discussion on HO requirements of NR-U | Intel Corporation |
| R4-2001440 | Discussion on HO requirements in NR-U | Nokia, Nokia Shanghai Bell |
| R4-2001555 | Discussion on handover in NR-U | Huawei, HiSilicon |
| R4-2002132 | Discussion regarding NR-U handover | Qualcomm |
| 8.1.4.3 | RRC connection mobility control [NR_unlic-Core] | |
| R4-2000047 | Discussion on UE behavior in RRC release with re-direction in NR-U | ZTE Corporation |
| R4-2000048 | Discussion on UE behavior in RRC re-establishment in NR-U | ZTE Corporation |
| R4-2000049 | Discussion on SIB reading in RRC procedures NR-U | ZTE Corporation |
| R4-2000926 | Discussion on RRC Re-establishment requirement for NR-U | MediaTek inc. |
| R4-2001359 | SIB1 acquisition time in NR-U | Ericsson |
| R4-2001442 | Discussion on the SI acquisition time in NR-U | Nokia, Nokia Shanghai Bell |
| R4-2001556 | Discussion on RRC connection mobility control in NR-U | Huawei, HiSilicon |
| R4-2001846 | Analysis of open issues in RRC re-establishment in NR-U | Ericsson |
| R4-2001847 | Analysis of open issues in RRC re-direction in NR-U | Ericsson |
| R4-2002133 | Discussion regarding NR-U RRC Mobility Control | Qualcomm |
| 8.1.4.4 | SCell activation/deactivation (delay and interruption) [NR_unlic-Core] | |
| R4-2000057 | Discussion on SCell activation delay in NR-U | ZTE Corporation |
| R4-2000715 | On Scell activation and deactivation requirements in NR-U | Qualcomm Incorporated |
| R4-2001557 | Discussion on SCell activation in NR-U | Huawei, HiSilicon |
| R4-2001841 | Introduction of activation and deactivation delay requirements for SCells operating with CCA | Qualcomm Incorporated |
| R4-2001930 | On SCell activation delay in NR-U | Ericsson |
| 8.1.4.5 | PSCell addition/release (delay and interruption) [NR_unlic-Core] | |
| R4-2000058 | Discussion on PSCell addition delay in NR-U | ZTE Corporation |
| R4-2000716 | On PSCell addition and release requirements in NR-U | Qualcomm Incorporated |
| R4-2000927 | Discussion on PSCell addition for NR-U | MediaTek inc. |
| R4-2001558 | Discussion on PSCell addition and release in NR-U | Huawei, HiSilicon |
| R4-2001842 | Introduction of addition and release of NR PSCell operating with CCA in EN-DC | Qualcomm Incorporated |
| R4-2001932 | On PSCell addition/release requirements in NR-U | Ericsson |
| 8.1.4.6 | Active TCI state switching [NR_unlic-Core] | |
| R4-2000717 | On active TCI switching requirements in NR-U | Qualcomm Incorporated |
| R4-2000928 | Discussion on TCI switch requirement for NR-U | MediaTek inc. |
| R4-2001559 | Discussion on Active TCI state switching in NR-U | Huawei, HiSilicon |
| R4-2001931 | On active TCI state switching requirements in NR-U | Ericsson |
| 8.1.4.7 | Interruptions due to operation in non-NR-U serving cells [NR_unlic-Core] | |
| R4-2001395 | Updates to SA NR interruption requirements for NR-U | Ericsson |
| 8.1.4.8 | Active BWP switching [NR_unlic-Core] | |
| R4-2001560 | Discussion on Active BWP switching in NR-U | Huawei, HiSilicon |
| R4-2001848 | Analysis of BWP switching requirement due to consistent UL failure | Ericsson |
| R4-2001849 | BWP switching requirement due to consistent UL failure in 38.133 | Ericsson |
| R4-2001850 | Interruption due to BWP switching at consistent UL failure in 36.133 | Ericsson |
| 8.1.4.9 | RLM and link recovery procedures [NR_unlic-Core] | |
| R4-2000050 | Discussion on RLM in NR-U | ZTE Corporation |
| R4-2000929 | Discussion on RLM requirement for NR-U | MediaTek inc. |
| R4-2000987 | On RLM requirement for NR-U | OPPO |
| R4-2001360 | Beam management in NR-U | Ericsson |
| R4-2001439 | On RLM requirements in NR-U | Nokia, Nokia Shanghai Bell |
| R4-2001561 | Discussion on RLM and link recovery in NR-U | Huawei, HiSilicon |
| R4-2001933 | On RLM in NR-U | Ericsson |
| R4-2001934 | Introduction of RLM requirements for NR-U | Ericsson |
| R4-2002130 | RLM and Link Recovery Procedure in NR-U | Qualcomm |
| 8.1.4.10 | Measurement requirements [NR_unlic-Core] | |
| R4-2000041 | CR to address NR-U in EN-DC SFTD measurements in 36.133 v2 | ZTE Corporation |
| R4-2000042 | Discussion on inter-RAT SFTD measurement towards NR-U | ZTE Corporation |
| R4-2000043 | CR to address NR-U in inter-RAT SFTD measurements in 36.133 | ZTE Corporation |
| R4-2000044 | [draft] LS on inter-RAT SFTD delay for NR-U | ZTE Corporation |
| R4-2000718 | Remaining issues on measurement requirements in NR-U | Qualcomm Incorporated |
| R4-2000719 | Draft LS on RSSI measurements in NR-U | Qualcomm Incorporated |
| R4-2000720 | On RSSI and CO measurements in NR-U | Qualcomm Incorporated |
| R4-2000780 | Remaining issues on cell detection and serving cell measurement for NR-U | Apple |
| R4-2000930 | Discussion on measurement on QCL-ed SSBs and measurement capability for NR-U | MediaTek inc. |
| R4-2000931 | Discussion on SFTD measurements towards NR-U with LBT | MediaTek inc. |
| R4-2001361 | L1-RSRP measurements in NR-U | Ericsson |
| R4-2001437 | On SSB index identification time in NR-U | Nokia, Nokia Shanghai Bell |
| R4-2001441 | On The impact of UL LBT failure in measurement reporting in NR-U | Nokia, Nokia Shanghai Bell |
| R4-2001443 | On L1-RSRP measurement requirements in NR-U | Nokia, Nokia Shanghai Bell |
| R4-2001562 | Discussion on measurement requirement in NR-U | Huawei, HiSilicon |
| R4-2001804 | CR to 38.133 to address NR-U inter-RAT measurements | Nokia, Nokia Shanghai Bell |
| R4-2001929 | On RSSI and channel occupancy measurement requirements | Ericsson |
| R4-2001935 | On the impact of UL LBT failures on measurement reporting delay | Ericsson |
| R4-2001936 | On intra-frequency measurements in NR-U | Ericsson |
| R4-2001937 | On inter-frequency measurements in NR-U | Ericsson |
| R4-2002086 | On inter-RAT SFTD under CCA | Ericsson |
| R4-2002087 | CR 36.133 (8.1.2.4) Inter-RAT SFTD under CCA | Ericsson |
| R4-2002285 | CR to 38.133 to address NR-U inter-RAT measurements | Nokia, Nokia Shanghai Bell |
| 8.1.4.11 | Measurement accuracy [NR_unlic-Core] | |
| R4-2000721 | On measurements accuracy requirements in NR-U | Qualcomm Incorporated |
| 8.1.4.12 | Measurement capability and reporting criteria [NR_unlic-Core] | |
| R4-2000045 | Discussion on RSSI and CO report mapping for NR-U v2 | ZTE Corporation |
| R4-2000722 | On measurement capabilities and reporting criteria | Qualcomm Incorporated |
| R4-2000932 | Discussion on measurement reporting criteria in NR-U | MediaTek inc. |
| R4-2001563 | Discussion on measurement capability in NR-U | Huawei, HiSilicon |
| R4-2001938 | On measurement reporting criteria for NR-U | Ericsson |
| 8.1.4.13 | Timing [NR_unlic-Core] | |
| R4-2000046 | Discussion on timing reference cell adjustment for NR-U | ZTE Corporation |
| R4-2000933 | Discussion on synchronization assumption and SSB index detection in NR-U | MediaTek inc. |
| R4-2000934 | Discussion on timing requirements in NR-U | MediaTek inc. |
| R4-2001710 | Draft CR on UE transmit timing accuracy and timing reference cell under DL LBT failure | Ericsson |
| R4-2001711 | On the timing reference cell adaptation under DL LBT failure in reference cell | Ericsson |
| R4-2002131 | Discussion regarding NR-U UL timing | Qualcomm |
| 8.1.4.14 | Others [NR_unlic-Core] | |
| R4-2001393 | Updates to clause 1-3 (General) for NR-U in 36.133 | Ericsson |
| R4-2001394 | Updates to clause 1-3 (General) for NR-U in 38.133 | Ericsson |
| R4-2001564 | Discussion on SI reading in NR-U | Huawei, HiSilicon |
| 8.2 | Cross Link Interference (CLI) handling and Remote Interference Management (RIM) for NR [NR_CLI_RIM] | |
| R4-2002172 | Email discussion summary for RAN4#94e_#49_NR_CLI_RIM_RRM | Moderator (LG Electronics) |
| R4-2002303 | Email discussion summary for RAN4#94e_#49_NR_CLI_RIM_RRM | Moderator (LG Electronics) |
| 8.2.2 | RRM core requirements maintenance (38.133) [NR_CLI_RIM-Core] | |
| R4-2000653 | Discussion on scheduling restriction for CLI measurements | Nokia, Nokia Shanghai Bell |
| R4-2000960 | Discussion on scheduling restriction update | LG Electronics Inc. |
| R4-2001621 | Discussion on accuracy requirements for CLI measurements | Huawei, HiSilicon |
| R4-2001622 | [draft] reply LS on CLI measurement capability | Huawei, HiSilicon |
| R4-2001623 | CR on CLI measurement requirements | Huawei, HiSilicon |
| R4-2002220 | CR on CLI measurement requirements | Huawei, HiSilicon |
| R4-2002221 | [draft] reply LS on CLI measurement capability | RAN4 |
| 8.2.3 | RRM perf. requirements (38.133) [NR_CLI_RIM-Perf] | |
| R4-2002222 | WF on CLI RRM Performance Requirements | LGE |
| 8.2.3.1 | CLI measurement accuracy [NR_CLI_RIM-Perf] | |
| R4-2000654 | Measurement accuracy for CLI SRS-RSRP measurement | Nokia, Nokia Shanghai Bell |
| R4-2000962 | SRS-RSRP measurement accuracy | LG Electronics Inc. |
| R4-2001624 | CR on CLI measurement accuracy requirements | Huawei, HiSilicon |
| R4-2002254 | CR on CLI measurement accuracy requirements | Huawei, HiSilicon |
| R4-2002255 | CR for conditions for cross link interference measurements (section B) | LGE |
| R4-2002343 | CR on CLI measurement accuracy requirements | Huawei, HiSilicon |
| 8.2.3.2 | Test cases [NR_CLI_RIM-Perf] | |
| R4-2000961 | Discussion on CLI performance test | LG Electronics Inc. |
| R4-2001625 | Discussion on RRM test cases for CLI | Huawei, HiSilicon |
| 8.2.3.3 | Others [NR_CLI_RIM-Perf] | |
| R4-2000958 | Discussion on minimum SRS RP level | LG Electronics Inc. |
| 8.3 | NR mobility enhancement [NR_Mob_enh] | |
| R4-2002173 | Email discussion summary for RAN4#94e_#50_NR_Mob_enh_RRM | Moderator (Intel Corporation) |
| R4-2002304 | Email discussion summary for RAN4#94e_#50_NR_Mob_enh_RRM | Moderator (Intel Corporation) |
| 8.3.2 | RRM core requirements (38.133) [NR_Mob_enh-Core] | |
| R4-2001417 | Testcases for LTE and NR mobility enhancements | Ericsson |
| R4-2002224 | WF on NR Mobility Enhancements RRM requirements | Intel |
| 8.3.2.1 | Handover with simultaneous Rx/Tx with source and target cells [NR_Mob_enh-Core] | |
| R4-2000375 | Discussion on remaining issues on DAPS handover | Intel Corporation |
| R4-2000376 | CR for DAPS handover RRM requirement | Intel Corporation |
| R4-2000723 | Remaining issues on DAPS HO | Qualcomm Incorporated |
| R4-2001413 | Remaining open issues on DAPS handover for NR | Ericsson |
| R4-2001414 | TP:Updates to DAPS handover requirements for NR | Ericsson |
| R4-2001571 | Further discussion on remaining issues on DAPS handover | Huawei, HiSilicon |
| R4-2001572 | CR on DAPS handover requirements | Huawei, HiSilicon |
| R4-2001797 | Discussion on dual active protocol stack handover | MediaTek inc. |
| R4-2002223 | CR on DAPS handover requirements | Huawei, HiSilicon |
| 8.3.2.2 | Conditional handover [NR_Mob_enh-Core] | |
| R4-2000377 | Discussion on remaining issues on CHO | Intel Corporation |
| R4-2000378 | CR for CHO RRM requirement | Intel Corporation |
| R4-2000724 | Remaining issues on conditional HO | Qualcomm Incorporated |
| R4-2001337 | Conditional handover for NR | Nokia, Nokia Shanghai Bell |
| R4-2001338 | CR Introduction of handover delay requirements for conditional handover (section 6.1) | Nokia, Nokia Shanghai Bell |
| R4-2001415 | Open issues for NR conditional handover | Ericsson |
| R4-2001416 | TP:Update to conditional handover requirements for NR | Ericsson |
| R4-2001573 | Further discussion on remaining issues on conditional handover | Huawei, HiSilicon |
| R4-2001798 | Discussion on requirement of conditional handover | MediaTek inc. |
| R4-2002225 | CR Introduction of handover delay requirements for conditional handover (section 6.1) | Nokia, Nokia Shanghai Bell |
| 8.3.2.3 | Conditional PSCell addition/change [NR_Mob_enh-Core] | |
| R4-2000379 | Discussion on conditional PSCell addition/change | Intel Corporation |
| R4-2000380 | CR for Conditional PSCell addition/change RRM requirement | Intel Corporation |
| R4-2000725 | On conditional PSCell addition and change | Qualcomm Incorporated |
| R4-2001574 | Discussion on conditional PSCell addition/change requirements | Huawei, HiSilicon |
| R4-2002226 | CR for Conditional PSCell addition/change RRM requirement | Intel Corporation |
| 8.4.1 | General [5G_V2X_NRSL] | |
| R4-2000703 | Reply LS to RAN1 on simultaneous transmission of PSFCH | Futurewei |
| R4-2000706 | Reply LS to RAN2 on UL-SL Prioritization | Futurewei |
| R4-2001214 | TR update TR38.886 v0.5.0 | LG Electronics France |
| R4-2001215 | Summary on E-mail discussion for NR V2X | LG Electronics France |
| R4-2001221 | TP on conclusion of NR V2X WI | LG Electronics France |
| R4-2002685 | Email discussion summary for RAN4#94e_#11_5G_V2X_NRSL_UE_TX | Moderator (LG Electronics) |
| R4-2002758 | WF on MPR/A-MPR simulation assumptions and parameters for simultaneous PSFCH transmission | Huawei |
| R4-2002759 | WF on MPR on S-SSB simulation assumptions and parameters | CATT |
| R4-2002760 | WF on on/off time mask for 5G V2X UE for single carrier SL transmission | LG Electronics |
| R4-2002784 | WF on on/off time switched period for TDM operation between LTE SL and NR SL transmission without dual PA capability | Qualcomm |
| R4-2002787 | WF on inter-band con-current operation and example band combinations in rel-16 | Dish Network |
| R4-2002790 | Reply LS to RAN2 on UL-SL Prioritization | Futurewei |
| R4-2002791 | WF on MPR/A-MPR simulation assumptions for NR V2X PC2 UE | Huawei, HiSilicon |
| R4-2002881 | Email discussion summary for RAN4#94e_#11_5G_V2X_NRSL_UE_TX | Moderator (LG Electronics) |
| 8.4.2.1 | Simulation Results [5G_V2X_NRSL-Core] | |
| R4-2000472 | MPR, A-MPR results for PSSCH/PSCCH transmission | Qualcomm Incorporated |
| R4-2000473 | MPR, A-MPR results for simultaneous PSFCH transmission | Qualcomm Incorporated |
| 8.4.2.2 | In-device coexistence [5G_V2X_NRSL-Core] | |
| R4-2000701 | TP on Indevice Coexistence | Futurewei |
| 8.4.3 | System parameters [5G_V2X_NRSL-Core] | |
| R4-2000471 | Switching time between NR SL and LTE SL | Qualcomm Incorporated |
| R4-2000567 | Remaining issues on channel raster for band n47 | vivo |
| R4-2000568 | CR on UE system parameters for NR V2X UE for TS 38.101-1 | vivo |
| R4-2000569 | CR on system parameters for NR V2X for TS 38.104 | vivo |
| R4-2001003 | TP on channel arrangement for NR V2X | vivo |
| R4-2002686 | Email discussion summary for RAN4#94e_#13_5G_V2X_NRSL_SysParameters | Moderator (vivo) |
| R4-2002793 | CR on UE system parameters for NR V2X UE for TS 38.101-1 | vivo |
| R4-2002795 | TP on channel arrangement for NR V2X | vivo |
| R4-2002882 | Email discussion summary for RAN4#94e_#13_5G_V2X_NRSL_SysParameters | Moderator (vivo) |
| 8.4.3.1 | Bands and bandwidth [5G_V2X_NRSL-Core] | |
| R4-2000570 | Channel bandwidths for NR V2X licensed bands | vivo |
| R4-2000571 | TP on channel bandwidths for NR V2X licensed band n38 | vivo |
| R4-2000902 | NR V2X licensed frequency bands for SL operation | CMCC |
| 8.4.3.2 | Others [5G_V2X_NRSL-Core] | |
| R4-2002028 | On channle raster for NR-V2X | Huawei, HiSilicon |
| 8.4.4 | UE RF requirements [5G_V2X_NRSL-Core] | |
| R4-2000688 | Addition of TX diversity into V2X | Qualcomm Incorporated |
| R4-2000690 | Declare Supported Post Antenna Gain for UE | Qualcomm Incorporated |
| R4-2002029 | On remaining NR-V2X UE RF requirements | Huawei, HiSilicon |
| R4-2002030 | CR for TS 38.101-1 Con-current operation for NR-V2X | Huawei, HiSilicon |
| R4-2002031 | draftCR for TS 38.101-3 Con-current operation for NR-V2X | Huawei, HiSilicon |
| R4-2002788 | CR for TS 38.101-1 Con-current operation for NR-V2X | Huawei, HiSilicon |
| R4-2002789 | draftCR for TS 38.101-3 Con-current operation for NR-V2X | Huawei, HiSilicon |
| 8.4.4.1 | Transmitter characteristics [5G_V2X_NRSL-Core ] | |
| R4-2000702 | NR V2X UE RF requirements considerations | Futurewei |
| R4-2000704 | On Simultaneous Transmission of PSFCH | Futurewei |
| R4-2000705 | On UL-SL Prioritization | Futurewei |
| R4-2001079 | [V2X] TP on PSFCH MPR requirements for NR V2X in band n47 | Huawei, HiSilicon |
| R4-2001080 | [V2X] MPR simulation results for PC3 NR V2X in band n47 | Huawei, HiSilicon |
| R4-2001081 | [V2X] MPR simulation results for PC2 NR V2X in band n47 | Huawei, HiSilicon |
| R4-2001082 | [V2X] TP to update MPR simulation assumption for NR V2X in band n47 | Huawei, HiSilicon |
| R4-2001083 | [V2X] TP on MPR requirements for PC3 NR V2X in band n47 | Huawei, HiSilicon |
| R4-2001084 | [V2X] TP on RF requirements for PC2 NR V2X UE in band n47 | Huawei, HiSilicon |
| R4-2001085 | [V2X] TP on S-SSB MPR requirements for NR V2X in band n47 | Huawei, HiSilicon |
| R4-2001216 | TP on additional On/OFF Switching Time Mask for TDM operation between LTE SL and NR SL at n47 | LG Electronics France |
| R4-2001217 | Draft CR on NR V2X UE Transmitter requirements for single carrier | LG Electronics France |
| R4-2001218 | TP on revised MPR simulation assumptions and update NR requirements to cover open issue | LG Electronics France |
| R4-2001220 | A-MPR simulation assumptions and initial results for NR V2X at n47 | LG Electronics France |
| R4-2001224 | Draft CR on additional On/OFF Switching Time Mask for TDM operation between LTE SL and NR SL at n47 | LG Electronics France |
| R4-2001240 | MPR simulation results for PSSCH/PSCCH NR V2X UE | LG Electronics Finland |
| R4-2001719 | MPR simulations results for multi-UE PSFCH transmission | LG Electronics Finland |
| R4-2002032 | draftCR for TS 38.101-1 PC2 RF requirements NR V2X | Huawei, HiSilicon |
| R4-2002033 | CR for TS 38.101-1 UL MIMO for NR-V2X | Huawei, HiSilicon |
| R4-2002761 | TP on revised MPR simulation assumptions and update NR requirements to cover open issue | LG Electronics France |
| R4-2002762 | MPR simulation results for PSSCH/PSCCH NR V2X UE | LG Electronics Finland |
| R4-2002763 | Draft CR on NR V2X UE Transmitter requirements for single carrier | LG Electronics France |
| R4-2002783 | A-MPR simulation assumptions and initial results for NR V2X at n47 | LG Electronics France |
| R4-2002785 | TP on additional On/OFF Switching Time Mask for TDM operation between LTE SL and NR SL at n47 | LG Electronics France |
| R4-2002786 | Draft CR on additional On/OFF Switching Time Mask for TDM operation between LTE SL and NR SL at n47 | LG Electronics France |
| R4-2002792 | CR for TS 38.101-1 UL MIMO for NR-V2X | Huawei, HiSilicon |
| R4-2002798 | Draft CR on additional On/OFF Switching Time Mask for TDM operation between LTE SL and NR SL at n47 | LG Electronics France |
| 8.4.4.2 | Receiver characteristics [5G_V2X_NRSL-Core ] | |
| R4-2000599 | CR for TS38.101-1, Introduce Rx requirements for NR V2X | CATT |
| R4-2000600 | CR for TS38.101-3, Introduce Rx requirements for NR V2X concurrent operation | CATT |
| R4-2000606 | CR for TS38.104, Introduce frequency band and channel arrangement for NR V2X | CATT |
| R4-2000607 | Dicussion on remaining RF requirements for NR V2X | CATT |
| R4-2000966 | TP on REFSENS for NR V2X | LG Electronics Inc. |
| R4-2002687 | Email discussion summary for RAN4#94e_#14_5G_V2X_NRSL_UE_RX | Moderator (CATT) |
| R4-2002794 | CR for TS38.104, Introduce frequency band and channel arrangement for NR V2X | CATT |
| R4-2002796 | CR for TS38.101-1, Introduce Rx requirements for NR V2X | CATT |
| R4-2002797 | CR for TS38.101-3, Introduce Rx requirements for NR V2X concurrent operation | CATT |
| R4-2002883 | Email discussion summary for RAN4#94e_#14_5G_V2X_NRSL_UE_RX | Moderator (CATT) |
| 8.4.5 | RRM core requirements (38.133) [5G_V2X_NRSL-Core] | |
| R4-2000939 | Discussion of remaining issues for NR V2X | LG Electronics Inc. |
| R4-2000943 | CR of NR V2X RRM(introduction & reliability of GNSS signal) | LG Electronics Inc. |
| R4-2002174 | Email discussion summary for RAN4#94e_#51_5G_V2X_NRSL_RRM_Part_1 | Moderator (LG Electronics) |
| R4-2002175 | Email discussion summary for RAN4#94e_#52_5G_V2X_NRSL_RRM_Part_2 | Moderator (MediaTek) |
| R4-2002228 | CR of NR V2X RRM(introduction & reliability of GNSS signal) | LG Electronics Inc. |
| R4-2002230 | WF on NR V2X RRM requirements | LGE, MediaTek |
| R4-2002231 | LS to RAN1 on PSSCH RSRP definition | MediaTek |
| R4-2002232 | Simulation assumption of PSSCH-RSRP and PSCCH-RSRP measurement | LGE |
| R4-2002305 | Email discussion summary for RAN4#94e_#51_5G_V2X_NRSL_RRM_Part_1 | Moderator (LG Electronics) |
| R4-2002306 | Email discussion summary for RAN4#94e_#52_5G_V2X_NRSL_RRM_Part_2 | Moderator (MediaTek) |
| 8.4.5.1 | Transmit timing requirements [5G_V2X_NRSL-Core] | |
| R4-2001575 | CR on introducing UE sidelink timing requirements for NR V2X | Huawei, HiSilicon |
| 8.4.5.2 | Synchronization requirements [5G_V2X_NRSL-Core] | |
| R4-2000768 | On NR V2X Synchronization Source Selection Requirement | Qualcomm, Inc. |
| R4-2000770 | On NR V2X Initiation/cease SLSS Tx with gNB/eNB as synchronization source Requirement | Qualcomm, Inc. |
| R4-2001027 | Discussion on NR V2X synchronization requirement | MediaTek inc. |
| R4-2001032 | CR on NR V2X initiation SLSS 38.133 -R16 | MediaTek inc. |
| R4-2001576 | Discussion on synchronization remaining issues for NR V2X | Huawei, HiSilicon |
| R4-2002229 | CR on NR V2X initiation SLSS 38.133 -R16 | MediaTek inc. |
| R4-2002342 | CR on NR V2X initiation SLSS 38.133 -R16 | MediaTek inc. |
| 8.4.5.3 | Measurement requirements [5G_V2X_NRSL-Core] | |
| R4-2000771 | On NR V2X Resource Selection requirement | Qualcomm, Inc. |
| R4-2000940 | Discussion of measurement accuracy for NR V2X | LG Electronics Inc. |
| R4-2000941 | Simulation assumption of PSSCH-RSRP and PSCCH-RSRP measurement | LG Electronics Inc. |
| R4-2001028 | Discussion on NR V2X measurement requirement | MediaTek inc. |
| R4-2001031 | Link-level simulation assumptions for NR SL L1-RSRP measurement | MediaTek inc. |
| R4-2001577 | Discussion on measurement remaining issues for NR V2X | Huawei, HiSilicon |
| 8.4.5.4 | Interruption requirements [5G_V2X_NRSL-Core] | |
| R4-2000579 | CR on interruption requirements for NR V2X | CATT |
| R4-2001029 | Discussion on NR V2X interruption requirement | MediaTek inc. |
| R4-2002256 | CR on interruption requirements for NR V2X | CATT |
| 8.4.5.5 | Unicast, groupcast related [5G_V2X_NRSL-Core] | |
| R4-2000769 | On NR V2X Distance-Based HARQ For Groupcast | Qualcomm, Inc. |
| R4-2001030 | Discussion on NR V2X unicast-groupcast related requirement | MediaTek inc. |
| 8.4.5.6 | Others [5G_V2X_NRSL-Core] | |
| R4-2000942 | Discussion of Annex.B for NR V2X side conditions | LG Electronics Inc. |
| 8.5 | Integrated Access and Backhaul for NR [NR_IAB] | |
| R4-2002371 | Email discussion summary for RAN4#94e_#80_NR_IAB_System_parameters | Moderator (Huawei) |
| R4-2002372 | Email discussion summary for RAN4#94e_#81_NR_IAB_Co-existence | Moderator (Nokia) |
| R4-2002373 | Email discussion summary for RAN4#94e_#82_NR_IAB_RF_Tx | Moderator (Qualcomm) |
| R4-2002374 | Email discussion summary for RAN4#94e_#83_NR_IAB_RF_Rx | Moderator (Samsung) |
| R4-2002483 | WF on IAB RX RF requirement | Samsung |
| R4-2002484 | WF on TS drafting referencing rules | Nokia |
| R4-2002485 | WF on IAB definitions | Ericsson |
| R4-2002489 | WF on CA and multi-carrier agreements | Ericsson |
| R4-2002490 | WF on IAB-MT ACS, IBB and ACLR in FR1 | ZTE |
| R4-2002491 | WF on IAB-MT ACS and IBB in FR2 | Ericsson |
| R4-2002492 | WF on IAB-MT ACLR and minimum Tx power in FR2 | Nokia |
| R4-2002494 | WF on IAB MT class definition | Samsung |
| R4-2002495 | WF on IAB-MT Tx power requirements | Huawei |
| R4-2002496 | WF on IAB Tx Signal Quality | Nokia |
| R4-2002498 | WF on IAB-DU Tx Requirements | ZTE |
| R4-2002503 | WF on IAB-MT Beam Correspondence | Qualcomm |
| R4-2002509 | Email discussion summary for RAN4#94e_#80_NR_IAB_System_parameters | Moderator (Huawei) |
| R4-2002510 | Email discussion summary for RAN4#94e_#81_NR_IAB_Co-existence | Moderator (Nokia) |
| R4-2002511 | Email discussion summary for RAN4#94e_#82_NR_IAB_RF_Tx | Moderator (Qualcomm) |
| R4-2002512 | Email discussion summary for RAN4#94e_#83_NR_IAB_RF_Rx | Moderator (Samsung) |
| 8.5.1 | General [NR_IAB-Core/Perf] | |
| R4-2000824 | FR1 IAB frequency band | Huawei, HiSilicon, China Telecom, China Unicom, BT plc |
| R4-2001186 | On multicarrier and CA for IAB | Ericsson |
| R4-2001887 | TP for TR _RF Requirements reference points | Ericsson |
| R4-2001888 | TP for TR _Spec organization | Ericsson |
| R4-2001901 | TP for TS _Conducted and radiated requirement reference points | Ericsson |
| R4-2001902 | TP for TS _Definitions | Ericsson |
| R4-2001904 | TP for TS _Relationship with other core specifications | Ericsson |
| R4-2002043 | [IAB] Discussion on drafting TS and referencing | Huawei |
| R4-2002123 | WF on IAB TS spec structure and terminology | Qualcomm |
| R4-2002487 | TP for TR _RF Requirements reference points | Ericsson |
| R4-2002488 | TP for TR _Spec organization | Ericsson |
| 8.5.2 | Co-existence study [NR_IAB-Core] | |
| R4-2000972 | simulation results for FR1 IAB coexistence study | ZTE Corporation |
| R4-2000973 | simulation results for FR2 IAB coexistence study | ZTE Corporation |
| R4-2000977 | In-band blocking for FR1 IAB MT | ZTE Corporation |
| R4-2000978 | In-band blocking for FR2 IAB MT | ZTE Corporation |
| R4-2001025 | TP to TR 38.xxx: Addition of antenna model and parameters in subclause 6.2 | Ericsson |
| R4-2001432 | TP to TR 38.xxx IAB-Node blocking, power class and coexistence requirements in FR2 | Nokia, Nokia Shanghai Bell |
| R4-2001708 | [IAB] TP to TR 38.xxx Antenna assumptions | Huawei |
| R4-2002493 | [IAB] TP to TR 38.xxx Antenna assumptions | Huawei |
| 8.5.3 | System parameters [NR_IAB-Core] | |
| R4-2000275 | TP for TS38.174: IAB system parameters | Samsung |
| R4-2000974 | Discussion on IAB MT channel bandwidth | ZTE Corporation |
| R4-2002044 | [IAB] TP to TS 38.174, clause 4 | Huawei |
| R4-2002045 | [IAB] TP to TS 38.174, clause 5 | Huawei |
| R4-2002486 | [IAB] TP to TS 38.174, clause 4 | Huawei |
| 8.5.4 | RF requirements [NR_IAB-Core] | |
| R4-2000964 | IAB DU RF Requirements | Qualcomm Incorporated |
| R4-2000965 | IAB MT RF Requirements | Qualcomm Incorporated |
| R4-2000975 | frequency error requirement for IAB | ZTE Corporation |
| R4-2000976 | switching time for IAB DU and MT | ZTE Corporation |
| R4-2000979 | Discussion on IAB MT OOBB | ZTE Corporation |
| R4-2000980 | Discussion on IAB MT BC requirement | ZTE Corporation |
| R4-2001019 | Technical background for IAB-Node reference sensitivity | Ericsson |
| R4-2001022 | Technical background for IAB-Node out-of-band receiver blocking | Ericsson |
| 8.5.4.1.1 | Transmitter characteristics [NR_IAB-Core] | |
| R4-2000618 | IAB frequency error requirement | CATT |
| R4-2000619 | Discussion of IAB MT power control accuracy requirement | CATT |
| R4-2000900 | Discussion on IAB Conducted Requirements | CMCC |
| 8.5.4.2.1 | Transmitter characteristics [NR_IAB-Core] | |
| R4-2000276 | Radiated transmit power and OTA output power for IAB-MT | Samsung |
| R4-2000277 | OTA output power dynamic for IAB-MT | Samsung |
| R4-2000278 | OTA transmit signal quality for IAB-MT | Samsung |
| R4-2000279 | OTA Unwanted emission for IAB-MT | Samsung |
| R4-2000901 | Discussion on IAB Radiated Tx Requirements | CMCC |
| R4-2001187 | On IAB MT beam correspondence | Ericsson |
| R4-2001280 | Definition of IAB-MT ACLR requirement in FR2 | Qualcomm Incorporated |
| R4-2001281 | Beam correspondence requirement for IAB-MT | Qualcomm Incorporated |
| R4-2001283 | On IAB-MT classes and dynamic range | Qualcomm Incorporated |
| R4-2001431 | TP to TR 38.xxx IAB-Node Frequency error requirements in FR2 | Nokia, Nokia Shanghai Bell |
| R4-2001433 | Switching time requirements between IAB-MT and IAB-DU | Nokia, Nokia Shanghai Bell |
| R4-2001434 | Beam correspondence requirement for IAB-Nodes | Nokia, Nokia Shanghai Bell |
| R4-2001436 | IAB-Node transmitter requirements for FR2 | Nokia, Nokia Shanghai Bell |
| R4-2001706 | [IAB] Discussion on beam correspondence | Huawei |
| R4-2001707 | [IAB] Discussion on transmitter OFF power | Huawei |
| R4-2001709 | [IAB] Discussion on power classes | Huawei |
| R4-2001865 | IAB MT ACLR | Ericsson |
| R4-2001866 | IAB MT TX dynamic range and min Tx power | Ericsson |
| R4-2001867 | IAB MT TX power | Ericsson |
| R4-2001868 | IAB class definition | Ericsson |
| R4-2001869 | IAB MT carrier leakage and IQ impag | Ericsson |
| R4-2001870 | IAB MT DU switching latency | Ericsson |
| R4-2001871 | IAB MT Frequency error | Ericsson |
| R4-2001872 | IAB MT power control requirement | Ericsson |
| R4-2001874 | TP for TR _9 IAB OTA Beam correspondence | Ericsson |
| R4-2001875 | TP for TR _9 IAB OTA IAB MT carrier leakage | Ericsson |
| R4-2001876 | TP for TR _9 IAB OTA IAB MT frequency error | Ericsson |
| R4-2001877 | TP for TR _9 IAB OTA IAB MT In-band emission | Ericsson |
| R4-2001878 | TP for TR _9 IAB OTA output power dynamics | Ericsson |
| R4-2001879 | TP for TR _9 IAB OTA output power | Ericsson |
| R4-2001880 | TP for TR _9 IAB OTA transmit ON_OFF power | Ericsson |
| R4-2001881 | TP for TR _9 IAB OTA transmitter intermodulation | Ericsson |
| R4-2001882 | TP for TR OTA unwanted emissions | Ericsson |
| R4-2001883 | TP for TR _9 radiated power | Ericsson |
| R4-2001886 | TP for TR _IAB classification | Ericsson |
| R4-2001889 | TP for TS _9 IAB output power | Ericsson |
| R4-2001890 | TP for TS _9 OTA Carrier leakage | Ericsson |
| R4-2001891 | TP for TS _9 OTA EVM equalizer spectrum flatness | Ericsson |
| R4-2001892 | TP for TS _9 OTA EVM | Ericsson |
| R4-2001893 | TP for TS _9 OTA In-band emissions | Ericsson |
| R4-2001894 | TP for TS _9 OTA output power dynamics | Ericsson |
| R4-2001895 | TP for TS _9 OTA TX OFF Power | Ericsson |
| R4-2001896 | TP for TS _9 OTA TX ON_OFF time mask | Ericsson |
| R4-2001897 | TP for TS _9 OTA unwanted emissions -ACLR _OBW | Ericsson |
| R4-2001898 | TP for TS _9 Radiated transmit power | Ericsson |
| R4-2001903 | TP for TS _IAB classes | Ericsson |
| R4-2002497 | TP for TR _9 IAB OTA transmitter intermodulation | Ericsson |
| 8.5.4.2.2 | Receiver characteristics [NR_IAB-Core] | |
| R4-2000280 | OTA REFSENS for IAB-MT | Samsung |
| R4-2000281 | Receiver dynamic range for FR2 IAB | Samsung |
| R4-2000282 | OTA in-band selectivity for IAB-MT | Samsung |
| R4-2000283 | OTA spurious emission for IAB | Samsung |
| R4-2000284 | OTA in-channel selectivity for IAB | Samsung |
| R4-2001020 | TP to TR 38.xxx: Addition of background information for FR2 reference sensitivity in subclause 10.3 | Ericsson |
| R4-2001021 | TP to TS 38.174: Addition of FR2 IAB reference sensitivity requirement text in clause 3 and clause 10 | Ericsson |
| R4-2001023 | TP to TR 38.xxx: Addition of background information for FR2 out-of-band blocking in subclause 10.6 | Ericsson |
| R4-2001024 | TP to TS 38.174: Addition of FR2 IAB out-of-band receiver blocking requirement in subclause 10.6 | Ericsson |
| R4-2001282 | Definition of IAB-MT in-band blocking requirement | Qualcomm Incorporated |
| R4-2001435 | IAB-Node receiver requirements for FR2 | Nokia, Nokia Shanghai Bell |
| R4-2001873 | IAB MT inband blocking and ACS | Ericsson |
| R4-2001884 | TP for TR _10 IAB OTA ACS | Ericsson |
| R4-2001885 | TP for TR _10 IAB OTA in-band blocking | Ericsson |
| R4-2001899 | TP for TS _10 OTA ACS | Ericsson |
| R4-2001900 | TP for TS _10 OTA Inband blocking | Ericsson |
| 8.5.5 | RRM core requirements (38.133) [NR_IAB-Core] | |
| R4-2000051 | Definition of macro and micro IAB nodes from RRM perspective | ZTE Corporation |
| R4-2001339 | RRM requirements for IAB | Nokia, Nokia Shanghai Bell |
| R4-2001852 | TP to TS 38.174 v0.0.1: Applicability of RRM requirements for different IAB classes | Ericsson |
| R4-2002176 | Email discussion summary for RAN4#94e_#53_NR_IAB_RRM | Moderator (Qualcomm) |
| R4-2002233 | WF on NR IAB RRM requirements | Qualcomm |
| R4-2002307 | Email discussion summary for RAN4#94e_#53_NR_IAB_RRM | Moderator (Qualcomm) |
| 8.5.5.1 | RRC connection mobility control [NR_IAB-Core] | |
| R4-2001549 | Discussion on RRC connection mobility control for IAB | Huawei, HiSilicon |
| R4-2001853 | TP to TS 38.174 v0.0.1: RRC re-establishment requirements for IAB MT | Ericsson |
| R4-2001854 | TP to TS 38.174 v0.0.1: RRC re-direction requirements for IAB MT | Ericsson |
| R4-2001855 | TP to TS 38.174 v0.0.1: PRACH requirements for IAB MT | Ericsson |
| R4-2002128 | RRC Connection Mobility Control in IAB Networks | Qualcomm |
| 8.5.5.2 | MT timing related requirements [NR_IAB-Core] | |
| R4-2000052 | MT timing requirements for IAB | ZTE Corporation |
| R4-2001856 | TP to TS 38.174 v0.0.1: IAB MT transmit timing requirements | Ericsson |
| R4-2001857 | TP to TS 38.174 v0.0.1: IAB MT TA accuracy requirements | Ericsson |
| R4-2001954 | Discussion on MT timing for IAB | Huawei, HiSilicon |
| R4-2001955 | TP to TS 38.174 MT Timing | Huawei, HiSilicon |
| R4-2002126 | IAB-MT timing related requirements | Qualcomm |
| 8.5.5.3 | DU timing related requirements [NR_IAB-Core] | |
| R4-2001858 | TP to TS 38.174 v0.0.1: Cell phase sync requirements for IAB DU | Ericsson |
| R4-2002125 | IAB-DU timing related requirements | Qualcomm |
| 8.5.5.4 | RLM requirements [NR_IAB-Core] | |
| R4-2000053 | RLM requirements for IAB MT | ZTE Corporation |
| R4-2000652 | Discussion on RLM requirement for IAB-MT | Samsung Electronics Co., Ltd |
| R4-2000889 | Discussion on RLM requirement for IAB-MT | Samsung |
| R4-2002127 | IAB-MT RLM requirements | Qualcomm |
| 8.5.5.5 | BFD/BFR requirements [NR_IAB-Core] | |
| R4-2000890 | Discussion on BFD and CBD requirement for IAB-MT | Samsung |
| R4-2002124 | IAB-MT BFD/BFR requirements | Qualcomm |
| 8.5.6 | EMC core requirements [NR_IAB-Core] | |
| R4-2001253 | further discussion on IAB EMC emission requirement | ZTE Corporation |
| R4-2001254 | further discussion on IAB EMC immunity requirement | ZTE Corporation |
| R4-2001255 | TP to TR IAB EMC emission requirements | ZTE Corporation |
| R4-2001256 | TP to TR IAB EMC General part | ZTE Corporation |
| R4-2001257 | TP to TR IAB EMC immunity requirements | ZTE Corporation |
| R4-2002348 | Way forward on IAB EMC requirements | ZTE Corporation |
| R4-2002452 | Way forward on IAB EMC requirements | ZTE Corporation |
| 8.6.3 | RRM core requirements (38.133) [LTE_NR_DC_CA_enh-Core] | |
| R4-2002177 | Email discussion summary for RAN4#94e_#54_LTE_NR_DC_CA_RRM | Moderator (Nokia) |
| R4-2002234 | WF on RRM Requirements for MR-DC | Nokia, Nokia Shanghai Bell |
| R4-2002235 | WF on NR Inter-RAT EMR requirements | Nokia, Nokia Shanghai Bell |
| R4-2002238 | WF on UE RRM requirements for dormancy Scell | Nokia, Nokia Shanghai Bell |
| R4-2002264 | Running CR to 36.133 for Multi-RAT Dual-Connectivity and Carrier Aggregation enhancements | nn |
| R4-2002265 | Running CR to 38.133 for Multi-RAT Dual-Connectivity and Carrier Aggregation enhancements | nn |
| R4-2002308 | Email discussion summary for RAN4#94e_#54_LTE_NR_DC_CA_RRM | Moderator (Nokia) |
| 8.6.3.1 | Asynchronous and synchronous NR-NR Dual Connectivity [LTE_NR_DC_CA_enh-Core] | |
| R4-2001626 | CR on Interruptions at SCell activation/deactivation in async NR-DC | Huawei, HiSilicon |
| 8.6.3.2 | Early Measurement reporting [LTE_NR_DC_CA_enh-Core] | |
| R4-2000988 | On MR-DC Early Measurement reporting | OPPO |
| R4-2002056 | Further discussion on early measurement reporting in MR-DC | Qualcomm Incorporated |
| 8.6.3.2.1 | NR measurements for EMR [LTE_NR_DC_CA_enh-Core] | |
| R4-2001340 | Early measurements and reporting in NR | Nokia, Nokia Shanghai Bell |
| R4-2001627 | Discussion on early measurement in NR | Huawei, HiSilicon |
| R4-2001795 | Discussion on LTE CRS based and NR SSB based measurement in NR IDLE/INACTIVE mode | MediaTek inc. |
| R4-2001927 | Further details on early measurement reporting requirements | Ericsson |
| R4-2001928 | Early measurement reporting requirements structure | Ericsson |
| 8.6.3.2.2 | LTE NR Inter-RAT EMR [LTE_NR_DC_CA_enh-Core] | |
| R4-2001341 | NR Inter-RAT measurements for early measurement reporting | Nokia, Nokia Shanghai Bell |
| R4-2001628 | Discussion on LTE – NR inter-RAT EMR | Huawei, HiSilicon |
| R4-2001796 | Discussion on NR SSB based measurement in LTE IDLE/INACTIVE mode | MediaTek inc. |
| 8.6.3.3.1 | Direct SCell activation [LTE_NR_DC_CA_enh-Core] | |
| R4-2000059 | On delay requirements for direct SCell activation in resume | ZTE Corporation |
| R4-2000060 | [CR] Add delay requirements for direct SCell activation in resume | ZTE Corporation |
| R4-2000061 | [CR] Add delay requirements for direct SCell activation in resume | ZTE Corporation |
| R4-2000062 | [CR] Delay requirements for direct SCell activation | ZTE Corporation |
| R4-2001011 | Direct SCell activation interruption requirements | NEC |
| R4-2001629 | Discussion on remaining issues for direct SCell activation | Huawei, HiSilicon |
| R4-2001630 | CR on direct SCell activation delay | Huawei, HiSilicon |
| R4-2002084 | On direct SCell activation | Ericsson |
| R4-2002085 | CR 38.133 (8.3.4-5) Corrections to Direct SCell activation | Ericsson |
| R4-2002236 | CR 38.133 (8.3.4-5) Corrections to Direct SCell activation | Ericsson |
| R4-2002237 | CR on direct SCell activation delay | Huawei, HiSilicon |
| 8.6.3.3.2 | SCell dormancy [LTE_NR_DC_CA_enh-Core] | |
| R4-2001342 | UE Requirements for Dormancy Scell | Nokia, Nokia Shanghai Bell |
| R4-2001631 | Discussion on RRM requirements for SCell dormancy | Huawei, HiSilicon |
| R4-2002059 | Discussion on Scell BWP dormancy | Qualcomm Incorporated |
| 8.7.1 | General [NR_UE_pow_sav] | |
| R4-2002688 | Email discussion summary for RAN4#94e_#15_NR_UE_pow_sav_RF | Moderator (CATT) |
| R4-2002799 | WF on NR UE power saving | CATT |
| R4-2002884 | Email discussion summary for RAN4#94e_#15_NR_UE_pow_sav_RF | Moderator (CATT) |
| 8.7.2 | Switching and interruption time [NR_UE_pow_sav] | |
| R4-2000601 | Further discussion on switching and interruption for maximum MIMO layer adaptation | CATT |
| R4-2000767 | Switching time for MIMO only change | Qualcomm, Inc. |
| R4-2000969 | Discussion on switching time for MIMO layer adaptation | ZTE Corporation |
| R4-2001758 | On switching time for MIMO layer/antenna number adaption | Huawei, HiSilicon |
| R4-2001793 | Discussion on UE dynamic adaptation to the maximum number of MIMO layers | MediaTek inc. |
| 8.7.3 | RRM core requirements (38.133) [NR_UE_pow_sav-Core] | |
| R4-2002178 | Email discussion summary for RAN4#94e_#55_NR_UE_pow_sav_RRM | Moderator (CATT) |
| R4-2002198 | Email discussion summary for RAN4#94e_#55_NR_UE_pow_sav_RRM | Moderator (CATT) |
| R4-2002309 | Email discussion summary for RAN4#94e_#55_NR_UE_pow_sav_RRM | Moderator (CATT) |
| 8.7.3.1 | RRM measurement relaxation [NR_UE_pow_sav-Core] | |
| R4-2000152 | Remaining issues on NR UE power saving | vivo |
| R4-2000157 | Draft LS on introducing thresholds for inter-frequency RRM relaxation for UE Power Saving | vivo |
| R4-2000158 | Evaluation of RRM relaxation for power saving | vivo |
| R4-2000575 | Further discussion on RRM measurement relaxation for NR power saving | CATT |
| R4-2000576 | CR on measurement relaxation in IDLE mode for UE power saving | CATT |
| R4-2000577 | CR for DCI based TCI state switch delay due to cross slot scheduling | CATT |
| R4-2000578 | CR for DCI based BWP switch delay due to cross slot scheduling | CMCC |
| R4-2000642 | RRM measurement relaxation for UE power saving | CMCC |
| R4-2000963 | Measurement relaxation for power saving | LG Electronics Inc. |
| R4-2000989 | On RRM measurement relaxation for power saving | OPPO |
| R4-2001343 | UE RRM Core requirements when applying UE power saving | Nokia, Nokia Shanghai Bell |
| R4-2001344 | LS on introduction of carrier specific thresholds for UE Power Saving schemes | Nokia, Nokia Shanghai Bell |
| R4-2001654 | Discussion on measurement relaxation in power saving | Huawei, HiSilicon |
| R4-2001754 | Discussions on RRM impact of NR UE power saving | Ericsson |
| R4-2001794 | Discussion on RRM measurement relaxation in IDLE/INACTIVE mode | MediaTek inc. |
| R4-2002137 | RRM measurement relaxation for power saving | Qualcomm |
| R4-2002239 | WF on RRM measurement relaxation for power saving | CATT |
| R4-2002326 | CR on measurement relaxation in IDLE mode for UE power saving | CATT |
| R4-2002338 | WF on RRM measurement relaxation for power saving | CATT |
| 8.7.3.2 | Requirements for MIMO layer adaptation [NR_UE_pow_sav-Core] | |
| R4-2000153 | Regarding switching and interruption timing requirement for MIMO layer adaption | vivo |
| R4-2000602 | CR on RRM requirement for maximum MIMO layer adaptation | vivo, CATT |
| R4-2000787 | On baseband requirement with MIMO layer adaptation | Apple |
| R4-2000990 | On requirements for MIMO layer adaptation for power saving | OPPO |
| R4-2001655 | Discussion on RRM requirement for MIMO layer adaption case2 | Huawei, HiSilicon |
| R4-2002136 | Interruption time during MIMO layer adaptation | Qualcomm |
| 8.8 | NR Positioning Support [NR_pos] | |
| R4-2002179 | Email discussion summary for RAN4#94e_#56_NR_pos_RRM_Part_1 | Moderator (Qualcomm) |
| R4-2002180 | Email discussion summary for RAN4#94e_#57_NR_pos_RRM_Part_2 | Moderator (Ericsson) |
| R4-2002275 | WF on NR Positioning gNB measurement requirements and report mapping | Ericsson |
| R4-2002276 | WF on NR Positioning measurement impact on RRM requirements | Qualcomm |
| R4-2002277 | WF on NR Positioning UE requirements | Qualcomm |
| R4-2002310 | Email discussion summary for RAN4#94e_#56_NR_pos_RRM_Part_1 | Moderator (Qualcomm) |
| R4-2002311 | Email discussion summary for RAN4#94e_#57_NR_pos_RRM_Part_2 | Moderator (Ericsson) |
| R4-2002328 | WF on NR Positioning UE requirements | Qualcomm |
| 8.8.1 | General (Work plan, rapporteur input) [NR_pos-Core/Perf] | |
| R4-2001947 | LS on UE measurement report mapping for UE positioning measurements in NR | Ericsson |
| R4-2002280 | LS on gNB measurements report mapping for NR Positioning | RAN4 |
| 8.8.2 | RRM core requirements (38.133) [NR_pos-Core] | |
| R4-2001632 | On report mapping for UE/gNB positioning measurement | Huawei, HiSilicon |
| R4-2001633 | [draft] reply LS on agreements related to NR Positioning | Huawei, HiSilicon |
| 8.8.2.1 | UE requirements [NR_pos-Core] | |
| R4-2000388 | Discussion on UE PRS processing behavior | Intel Corporation |
| R4-2001918 | UE behaviour for processing DL PRS without measurement gap | Nokia, Nokia Shanghai Bell |
| 8.8.2.1.2 | PRS-RSTD measurements [NR_pos-Core] | |
| R4-2000389 | Further Discussion on NR PRS RSTD Requirements for UE | Intel Corporation |
| R4-2000589 | Discussion on RSTD measurement requirements | CATT |
| R4-2000731 | On PRS-RSTD measurements for NR positioning | Qualcomm Incorporated |
| R4-2000783 | On RSTD measurement report mapping for NR positioning | Apple |
| R4-2000784 | LS on RSTD measurement report mapping for NR positioning | Apple |
| R4-2000998 | Discussion on PRS-RSTD measurement | MediaTek inc. |
| R4-2001637 | Discussion on RSTD measurement | Huawei, HiSilicon |
| R4-2001941 | On PRS RSTD measurements | Ericsson |
| R4-2001942 | On PRS RSTD measurement report mapping | Ericsson |
| R4-2001943 | Measurement report mapping for PRS RSTD | Ericsson |
| 8.8.2.1.3 | PRS-RSRP measurements [NR_pos-Core] | |
| R4-2000590 | Discussion on PRS-RSRP measurement requirements | CATT |
| R4-2000732 | On PRS-RSRP measurements for NR positioning | Qualcomm Incorporated |
| R4-2000999 | Discussion on PRS-RSRP measurement | MediaTek inc. |
| R4-2001638 | Discussion on PRS-RSRP measurement | Huawei, HiSilicon |
| R4-2001944 | On PRS-RSRP measurements | Ericsson |
| R4-2001945 | On PRS-RSRP measurement report mapping | Ericsson |
| R4-2001946 | Measurement report mapping for PRS-RSRP | Ericsson |
| R4-2002289 | Measurement report mapping for PRS-RSRP | Ericsson |
| 8.8.2.1.4 | Rx-Tx time difference measurements [NR_pos-Core] | |
| R4-2000603 | Discussion on Rx-Tx timing difference measurement | CATT |
| R4-2000604 | Discussion on definition of Rx-Tx timing difference measurement | CATT |
| R4-2000733 | On UE Rx-Tx time difference measurement for NR positioning | Qualcomm Incorporated |
| R4-2001000 | Discussion on UE Rx-Tx time difference measurements | MediaTek inc. |
| R4-2001639 | Discussion on Rx-Tx time difference measurement | Huawei, HiSilicon |
| R4-2001859 | UE Rx-Tx Measurement Report Mapping in NR | Ericsson |
| R4-2001940 | On UE Rx-Tx measurements | Ericsson |
| 8.8.2.1.5 | SSB and CSI-RS RSRP/RSRQ measurements [NR_pos-Core] | |
| R4-2000734 | On positioning requirements for E-CID | Qualcomm Incorporated |
| R4-2001948 | NR E-CID measurement requirements | Ericsson |
| R4-2001949 | NR E-CID reporting criteria requirements | Ericsson |
| R4-2001950 | LS on NR E-CID measurements | Ericsson |
| R4-2002288 | NR E-CID measurement requirements | Ericsson |
| 8.8.2.1.6 | Link-level evaluations for PRS-RSTD and PRS-RSRP [NR_pos-Core] | |
| R4-2000391 | Link-level simulation results for RSTD measurement | Intel Corporation |
| R4-2000591 | Link-level simulation results of PRS RSRP | CATT |
| R4-2000592 | Link-level simulation results of PRS RSTD | CATT |
| R4-2000735 | Link-level PRS-RSTD simulation results | Qualcomm Incorporated |
| R4-2001001 | Link level evaluation on PRS-RSRP and PRS-RSTD | MediaTek inc. |
| R4-2001635 | Link level simulation results for PRS measurement | Huawei, HiSilicon |
| R4-2001636 | Updated link level simulation assumption for RSTD and RSRP | Huawei, HiSilicon |
| R4-2001939 | Link simulation results for NR RSTD | Ericsson |
| R4-2002287 | Updated link level simulation assumption for RSTD and RSRP | Huawei, HiSilicon |
| 8.8.2.2 | gNB requirements [NR_pos-Core] | |
| R4-2000054 | Discussion on gNB requirements and report mapping | ZTE Corporation |
| R4-2000390 | Considerations on gNB measurement requirements for NR positioning | Intel Corporation |
| R4-2000736 | on gNB requirements for NR positioning | Qualcomm Incorporated |
| R4-2001196 | Views on gNB measurement for NR positioning | NTT DOCOMO, INC. |
| R4-2001496 | On gNB measurement requirements | Ericsson |
| R4-2001634 | Discussion on gNB requirements for NR positioning | Huawei, HiSilicon, CMCC |
| R4-2001919 | On gNB measurement requirements for NR positioning | Nokia, Nokia Shanghai Bell |
| 8.8.2.3 | Impact on existing RRM requirements [NR_pos-Core] | |
| R4-2000605 | Further discussion on impact of positioning measurement on RRM requirements | CATT |
| R4-2000737 | On Impact of NR positioning on existing RRM requirements | Qualcomm Incorporated |
| R4-2001640 | Impact of PRS measurement on existing RRM requirements | Huawei, HiSilicon |
| 8.8.2.4 | Others [NR_pos-Core] | |
| R4-2000593 | Discussion on frequency layer and measurement gap | CATT |
| R4-2000738 | On UE-based positioning requirements | Qualcomm Incorporated |
| 8.9.1 | Demodulation and CSI requirements [NR_L1enh_URLLC-Perf] | |
| R4-2002381 | Email discussion summary for RAN4#94e_#90_NR_L1enh_URLLC_Demod_Test | Moderator (Ericsson) |
| R4-2002382 | Email discussion summary for RAN4#94e_#91_NR_L1enh_URLLC_Demod_Requirements | Moderator (Huawei) |
| R4-2002422 | Way Forward on parameters and test methodology for URLLC ultra-low BLER test | Ericsson |
| R4-2002428 | Way forward for NR UE URLLC performance requirements | Intel |
| R4-2002429 | Way forward for NR BS URLLC performance requirements | Huawei, HiSilicon |
| R4-2002519 | Email discussion summary for RAN4#94e_#90_NR_L1enh_URLLC_Demod_Test | Moderator (Ericsson) |
| R4-2002520 | Email discussion summary for RAN4#94e_#91_NR_L1enh_URLLC_Demod_Requirements | Moderator (Huawei) |
| 8.9.1.1 | Test feasibility [NR_L1enh_URLLC-Perf] | |
| R4-2000370 | Discussion on test feasibility and methodology for URLLC | Intel Corporation |
| R4-2000566 | Simulation results for URLCC device test times | Rohde & Schwarz |
| R4-2001178 | URLLC error floor test | Ericsson |
| R4-2001483 | Discussion and simulation results for URLLC high reliability test feasibility | Huawei, HiSilicon |
| R4-2001695 | On NR Rel-16 high reliability BS demodulation test feasibility and methodology | Nokia, Nokia Shanghai Bell |
| R4-2002115 | Views on URLLC Test Feasibility | Qualcomm Incorporated |
| 8.9.1.2 | UE demodulation and CSI requirements (38.101-4) [NR_L1enh_URLLC-Perf] | |
| R4-2000371 | Discussion on test cases for URLLC | Intel Corporation |
| R4-2000944 | Discussion on UE performance requirements for URLLC | NTT DOCOMO, INC. |
| R4-2001484 | Discussion and simulation results for URLLC UE PDSCH demodulation requirements for high reliability | Huawei, HiSilicon |
| R4-2001485 | Discussion on URLLC UE performance requriements for low latency | Huawei, HiSilicon |
| R4-2001486 | Discussion on URLLC UE CQI reporting requrements | Huawei, HiSilicon |
| R4-2001738 | Vies on UE demodulation test for slot aggregation | Ericsson |
| R4-2001739 | Aspects of Rel-15 UE candidate features | Ericsson |
| R4-2002142 | Views on URLLC Test Cases | Qualcomm Incorporated |
| 8.9.1.3 | BS demodulation requirements (38.104) [NR_L1enh_URLLC-Perf] | |
| R4-2000313 | View on BS demodulation requirement for URLLC in NR Rel-16 | Samsung |
| R4-2001179 | Proposals for BS slot aggregation requirement | Ericsson |
| R4-2001180 | Proposals for BS non-slot requirement | Ericsson |
| R4-2001181 | Proposal for BS grant free transmission requirement | Ericsson |
| R4-2001182 | Proposal for BS PUCCH requirement | Ericsson |
| R4-2001197 | Views on NR BS performance for URLLC | NTT DOCOMO, INC. |
| R4-2001487 | Discussion and simulation results for URLLC BS PUSCH demodulation requirements for high reliability | Huawei, HiSilicon |
| R4-2001488 | Discussion on URLLC BS performance requirements for low latency | Huawei, HiSilicon |
| R4-2001489 | Discussion on introduction of PUCCH demodulation performance requirements for URLLC | Huawei, HiSilicon |
| R4-2001696 | On NR Rel-16 high reliability BS demodulation requirements | Nokia, Nokia Shanghai Bell |
| 8.10 | Single radio voice call continuity from 5G to 3G (SRVCC) [SRVCC_NR_to_UMTS-Core] | |
| R4-2002181 | Email discussion summary for RAN4#94e_#58_SRVCC_NR_to_UMTS_RRM | Moderator (Huawei, HiSilicon) |
| R4-2002312 | Email discussion summary for RAN4#94e_#58_SRVCC_NR_to_UMTS_RRM | Moderator (Huawei, HiSilicon) |
| 8.10.1 | RRM core requirements maintenance (38.133) [SRVCC_NR_to_UMTS-Core] | |
| R4-2001673 | Correction on handover requirements for SRVCC | Huawei, HiSilicon |
| R4-2002240 | Correction on handover requirements for SRVCC | Huawei, HiSilicon |
| 8.10.2 | RRM perf requirements (38.133) [SRVCC_NR_to_UMTS-Perf] | |
| R4-2001418 | Test aspects of sRVCC for NR | Ericsson |
| R4-2001672 | Test case list for SRVCC | Huawei, HiSilicon |
| R4-2002241 | WF on SRVCC RRM test cases | Huawei, HiSilicon |
| 8.11.1.1 | DMRS enhancement with PI/2 BPSK [NR_eMIMO-Core] | |
| R4-2000470 | Pi/2 BPSK DMRS investigation | Qualcomm Incorporated |
| R4-2000517 | PI/2 BPSK MPR simulations with new REL16 DMRS | Nokia, Nokia Shanghai Bell |
| R4-2002035 | On eMIMO full power transmission | Huawei, HiSilicon |
| R4-2002689 | Email discussion summary for RAN4#94e_#16_NR_eMIMO_UE_RF | Moderator (Samsung) |
| R4-2002800 | WF on MPR with Pi/2 BPSK DMRS | Qualcomm |
| R4-2002801 | WF on Uplink Full Power Transmission | vivo |
| R4-2002885 | Email discussion summary for RAN4#94e_#16_NR_eMIMO_UE_RF | Moderator (Samsung) |
| 8.11.1.2 | Uplink Tx Full Power transmission [NR_eMIMO-Core] | |
| R4-2000315 | Further discussion on Uplink full power transmission | Samsung |
| R4-2000469 | TX full power capability | Qualcomm Incorporated |
| R4-2000751 | Discussion on UE RF requirments for eMIMO UL Full power Tx | vivo |
| R4-2001230 | About full power transmission tests in eMIMO | OPPO |
| R4-2001322 | Verification of FP transmission and power-class indication for full power with two layers | Ericsson |
| R4-2002036 | On Pi_2 BPSK DMRS | Huawei, HiSilicon |
| 8.11.2 | RRM core requirements (38.133) [NR_eMIMO-Core] | |
| R4-2002182 | Email discussion summary for RAN4#94e_#59_NR_eMIMO_RRM | Moderator (Samsung) |
| R4-2002242 | WF on NR eMIMO RRM requirements | Samsung |
| R4-2002313 | Email discussion summary for RAN4#94e_#59_NR_eMIMO_RRM | Moderator (Samsung) |
| 8.11.2.1 | L1-SINR [NR_eMIMO-Core] | |
| R4-2000285 | On the Remaining Issues for L1-SINR Measurement Requirement | Samsung |
| R4-2000286 | Simulation Results for L1-SINR Measurement Accuracy | Samsung |
| R4-2000287 | Simulation Results Summary for L1-SINR Measurement Accuracy | Samsung |
| R4-2000288 | CR to TS38.133 on L1-SINR Measurement Requirement (Section 3.3 and 9) | Samsung |
| R4-2000384 | Discussion about L1-SINR measurement requirements | Intel Corporation |
| R4-2000635 | Simulation results on L1-SINR | CMCC |
| R4-2000935 | Discussion on RRM requirements for L1-SINR | MediaTek inc. |
| R4-2000936 | Discussion on L1-SINR delay requirement | MediaTek inc. |
| R4-2000937 | Discussion on L1-SINR accuracy requirement | MediaTek inc. |
| R4-2000997 | CR on SS-SINR and CSI-SINR measurement report mapping (section 10.1.16.1) | OPPO |
| R4-2001362 | L1-SINR measurement period | Ericsson |
| R4-2001578 | Discussion on L1-SINR measurement requirements for NR eMIMO | Huawei, HiSilicon |
| R4-2001579 | Discussion on measurement restrictions for L1-SINR measurement | Huawei, HiSilicon |
| R4-2002120 | RRM requirements for L1-SINR estimation | Qualcomm |
| 8.11.2.2 | SCell Beam failure recovery [NR_eMIMO-Core] | |
| R4-2000289 | On the Remaining Issues for SCell Beam Failure Recovery RRM Requirement | Samsung |
| R4-2000290 | CR to TS38.133 on SCell BFD and CBD (Section 8.5) | Samsung |
| R4-2000291 | CR to TS38.133 on SCell BFRQ Procedure (Section 8.5) | Samsung |
| R4-2000938 | Discussion on RRM requirements for BFR on Scell | MediaTek inc. |
| R4-2001580 | discussion on SCell BFR requiremetns for NR eMIMO | Huawei, HiSilicon |
| R4-2002121 | RRM requirements for SCell BFD, CBD and BFR | Qualcomm |
| 8.11.2.3 | DL/UL beam indication with reduced latency and overhead [NR_eMIMO-Core] | |
| R4-2000292 | On the Remaining Issues for Enhancement on UL/DL Transmit Beam Selection with Reduced Latency and Overhead | Samsung |
| R4-2002122 | DL/UL beam indication with reduced latency and overhead | Qualcomm |
| 8.11.3 | Demodulation and CSI requirements [NR_eMIMO-Perf] | |
| R4-2002383 | Email discussion summary for RAN4#94e_#92_NR_eMIMO_Demod | Moderator (Samsung) |
| R4-2002419 | WF on demodulation and CSI requirement of NR eMIMO | Samsung |
| R4-2002420 | WF on PDSCH demodulation requirement based on multi-TRP/panel transmission for NR eMIMO | Huawei |
| R4-2002421 | WF on PMI reporting requirement for NR eMIMO | Qualcomm |
| R4-2002521 | Email discussion summary for RAN4#94e_#92_NR_eMIMO_Demod | Moderator (Samsung) |
| 8.11.3.1 | General [NR_eMIMO-Perf] | |
| R4-2000319 | Overview on Rel-16 eMIMO performance requirements | Samsung |
| R4-2000352 | Views on test cases for eMIMO | Qualcomm Incorporated |
| R4-2001740 | Discussion on demodulation requirements for Rel-16 NR eMIMO | Intel Corporation |
| 8.11.3.2 | Demodulation requirements [NR_eMIMO-Perf] | |
| R4-2000322 | Test case design for DL multi-pannel/TRP transmission | Samsung |
| R4-2000324 | Simulation assumption for eMIMO PDSCH test cases with multi-pannel/TRP transmission | Samsung |
| R4-2001363 | UE demodulation requirements for eMIMO | Ericsson |
| R4-2001466 | Discussion on UE performance requirements for Multi-TRP in NR eMIMO | Huawei, HiSilicon |
| R4-2001467 | Discussion on other UE performance requirements for NR eMIMO | Huawei, HiSilicon |
| R4-2001469 | Discussion on BS performance requirements for Multi-TRP in NR eMIMO | Huawei, HiSilicon |
| R4-2001470 | Discussion on other BS performance requirements for NR eMIMO | Huawei, HiSilicon |
| 8.11.3.3 | CSI requirements [NR_eMIMO-Perf] | |
| R4-2000320 | Test case design for Enhanced Type II codebook | Samsung |
| R4-2000321 | Initial simulation results for PMI reporting with enhanced type II codebook | Samsung |
| R4-2000323 | Simulation assumption for eMIMO PMI test cases with advanced Type II codebook | Samsung |
| R4-2001468 | Discussion on CSI enhancement demodulation performance requirement for NR eMIMO | Huawei, HiSilicon |
| R4-2001735 | Discussion on CSI requirements under interference | Ericsson |
| 8.12 | Add support of NR DL 256QAM for FR2 [NR_DL256QAM_FR2] | |
| R4-2002690 | Email discussion summary for RAN4#94e_#17_NR_DL256QAM_FR2 | Moderator (China Telecom) |
| R4-2002803 | WF on the requirements for FR2 DL 256QAM | China Telecom |
| R4-2002886 | Email discussion summary for RAN4#94e_#17_NR_DL256QAM_FR2 | Moderator (China Telecom) |
| 8.12.1 | General (Ad-hoc MoM/TR maintenance) [NR_DL256QAM_FR2] | |
| R4-2000909 | Draft TR 38.883 for FR2 DL 256QAM v1.1.0 | China Telecom |
| 8.12.2 | BS RF core requirements (38.104) [NR_DL256QAM_FR2] | |
| R4-2000910 | TP for TR 38.883 BS RF requirements for FR2 DL 256QAM | China Telecom |
| R4-2001189 | NR BS TX EVM for FR2 DL 256QAM | NTT DOCOMO, INC. |
| R4-2001426 | CR to TS 38.104 Introduction of FR2 DL 256QAM | Nokia, Nokia Shanghai Bell, China Telecom, Verizon, NTT Docomo, T-Mobile |
| R4-2001427 | CR to TS 38.141-2: Introduction of FR2 DL 256QAM | Nokia, Nokia Shanghai Bell, China Telecom, Verizon, NTT Docomo, T-Mobile |
| R4-2001729 | CR to TS 38.104: Addition of EVM for 256 QAM | Ericsson |
| R4-2002103 | CR to TS 38.141-2: Addition of EVM for 256 QAM | Ericsson Inc. |
| R4-2002802 | CR to TS 38.104 Introduction of FR2 DL 256QAM | Nokia, Nokia Shanghai Bell, China Telecom, Verizon, NTT Docomo, T-Mobile |
| 8.12.3 | UE RF core requirements (38.101-2) [NR_DL256QAM_FR2] | |
| R4-2000823 | UE maximum input level for DL 256QAM | Huawei, HiSilicon |
| R4-2000911 | TP for TR 38.883 UE RF requirements for FR2 DL 256QAM | China Telecom |
| R4-2000954 | Discussion on FR2 Maximum Input Level requirements for 256QAM | Intel Corporation |
| R4-2001190 | NR UE maximum input level for FR2 DL 256QAM | NTT DOCOMO, INC. |
| R4-2001425 | CR to TS 38.101-2: Introduction of FR2 DL 256QAM | Nokia, Nokia Shanghai Bell, China Telecom, Verizon, NTT Docomo, T-Mobile |
| 8.13.1 | RF core requirements [NR_RF_FR1] | |
| R4-2000069 | Time masks for ULSUP in R16 | Huawei, HiSilicon |
| R4-2000070 | CR to 38.101-3 on time masks for ULSUP in R16 | Huawei, HiSilicon |
| R4-2000754 | CR for TS 38.101-1: Corrections for n48 receiver requirements | MediaTek Inc. |
| R4-2001323 | UE behavior and time masks for ULSUP-TDM | Ericsson |
| R4-2002691 | Email discussion summary for RAN4#94e_#18_NR_RF_FR1_Part_1 | Moderator (Huawei, HiSilicon) |
| R4-2002804 | WF on emission RF requirement for intra-band contiguous UL CA | Huawei, HiSilicon |
| R4-2002805 | WF on MPR requirement for intra-band contiguous UL CA | Huawei, HiSilicon |
| R4-2002812 | WF on RF architecture for intra-band UL non-contiguous CA | Qualcomm |
| R4-2002813 | WF on testability of transient period capability | Huawei, HiSilicon |
| R4-2002814 | LS on testability of transient period capability | Huawei, HiSilicon |
| R4-2002887 | Email discussion summary for RAN4#94e_#18_NR_RF_FR1_Part_1 | Moderator (Huawei, HiSilicon) |
| R4-2002908 | CR for TS 38.101-1: Corrections for n48 receiver requirements | MediaTek Inc. |
| 8.13.1.1 | Almost contiguous allocations for CP-OFDM UL for FR1 [NR_RF_FR1] | |
| R4-2001762 | CR for 38.101-1 almost contiguous resource allocation | Huawei, HiSilicon |
| 8.13.1.2 | Intra-band contiguous DL CA for FR1 [NR_RF_FR1] | |
| R4-2000234 | CR for 38.101-1 to introduce BCS1 for CA_n77C and CA_n78C | Huawei, HiSilicon, CKH IOD UK |
| R4-2001077 | CR for 38.101-1 to correct bandwidth class B | Huawei, HiSilicon |
| R4-2001385 | Problems with CA channel arrangement | Nokia, Nokia Shanghai Bell |
| R4-2001771 | CR for intra-band CA configuration and DL requirement | Huawei, HiSilicon |
| R4-2002810 | CR for 38.101-1 to introduce BCS1 for CA_n77C and CA_n78C | Huawei, HiSilicon, CKH IOD UK |
| R4-2002811 | CR for intra-band CA configuration and DL requirement | Huawei, HiSilicon |
| 8.13.1.3 | Intra-band non-contiguous DL CA for FR1 for generic and n77 and n78 [NR_RF_FR1] | |
| R4-2001074 | CR for 38.101-1: simply intra-band CA operating band table in clause 5.2A.1 | Huawei, HiSilicon |
| 8.13.1.4 | Intra-band contiguous UL CA for FR1 power class 3 [NR_RF_FR1] | |
| R4-2000093 | Intra-band Contiguous ULCA MPR | Qualcomm Incorporated |
| R4-2000711 | [NRULCA] Definition of Intra-band Contiguous UL CA Allocation Types | Skyworks Solutions Inc. |
| R4-2000712 | [NRULCA] Definition of Intra-band Contiguous UL CA Bandwidths | Skyworks Solutions Inc. |
| R4-2000713 | [NRULCA] PC3 Back-off Measurements for NR intra-band contiguous UL CA | Skyworks Solutions Inc. |
| R4-2001129 | [NRULCA] Bandwidth Limitation in FR1 UL CA | Skyworks Solutions Inc. |
| R4-2001756 | on FR1 UL CA MPR requirement Rel-16 | Huawei, HiSilicon |
| R4-2001759 | CR on FR1 UL CA MPR requirement Rel-16 | Huawei, HiSilicon |
| R4-2001772 | CR for intra-band UL CA emission requirement | Huawei, HiSilicon |
| R4-2001773 | CR for intra-band UL CA output power | Huawei, HiSilicon |
| R4-2001774 | CR for intra-band UL CA signal quality | Huawei, HiSilicon |
| R4-2002806 | CR for intra-band UL CA output power | Huawei, HiSilicon |
| R4-2002807 | CR for intra-band UL CA signal quality | Huawei, HiSilicon |
| R4-2002808 | CR for intra-band UL CA emission requirement | Huawei, HiSilicon |
| R4-2002809 | CR on FR1 UL CA MPR requirement Rel-16 | Huawei, HiSilicon |
| 8.13.1.5 | Intra-band non-contiguous UL CA for FR1 power class [NR_RF_FR1] | |
| R4-2000104 | Intra-band non-contiguous ULCA requirements and MPR connsideration | Qualcomm Incorporated |
| R4-2002051 | draftCR for TS 38.101-1 intra-band UL contiguous CA combinations | Huawei, HiSilicon |
| 8.13.1.6 | Switching period between case 1 and case 2 [NR_RF_FR1] | |
| R4-2000064 | Discussion on the switching between 1Tx carrier and 2Tx carrier | Huawei, HiSilicon |
| R4-2000066 | CR to 38.101-1 on UE requirements for switching between 1Tx carrier and 2Tx carrier | Huawei, HiSilicon |
| R4-2000067 | CR to 38.101-3 on UE requirements for switching between 1Tx carrier and 2Tx carrier | Huawei, HiSilicon |
| R4-2000113 | Switching time details | Qualcomm Incorporated |
| R4-2000125 | Discussion on potential gain of large switching periods | vivo |
| R4-2000131 | RF time mask requirements to allow Tx switching between two uplink carriers | China Telecom |
| R4-2000132 | CR to TS 38.101-1: Switching time mask between two uplink carriers in UL CA and SUL | China Telecom |
| R4-2000133 | CR to TS 38.101-3: Switching time mask between two uplink carriers in EN-DC | China Telecom |
| R4-2000134 | LS on UE capability for switching between two uplink carriers | China Telecom |
| R4-2000628 | discussion on open issue for Tx switching between 2 uplink carriers | CATT |
| R4-2000643 | Requirements for switching between case1 and case2 | CMCC |
| R4-2000810 | Further consideration on uplink carrier switching | ZTE Wistron Telecom AB |
| R4-2001307 | Switching time between NR between FR1 uplink carriers | MediaTek Inc. |
| R4-2001428 | CR to TS 38.101-1: Time mask requirements for switching between 1Tx and 2Tx transmissions for inter-band UL CA | Nokia, Nokia Shanghai Bell |
| R4-2001429 | CR to TS 38.101-3: Time mask requirements for switching between 1Tx and 2Tx transmissions for inter-band EN-DC without SUL | Nokia, Nokia Shanghai Bell |
| R4-2001430 | Switching between case 1 and case 2 for two NR FR1 carriers | Nokia, Nokia Shanghai Bell |
| R4-2002692 | Email discussion summary for RAN4#94e_#19_NR_RF_FR1_Part_2 | Moderator (China Telecom) |
| R4-2002815 | WF on RF requirements for Tx switching between two uplink carriers | China Telecom |
| R4-2002816 | LS on Tx switching between two uplink carriers | RAN4 |
| R4-2002817 | CR to TS 38.101-1: Switching time mask between two uplink carriers in UL CA and SUL | China Telecom |
| R4-2002818 | CR to TS 38.101-3: Switching time mask between two uplink carriers in EN-DC | China Telecom |
| R4-2002888 | Email discussion summary for RAN4#94e_#19_NR_RF_FR1_Part_2 | Moderator (China Telecom) |
| 8.13.1.7 | Transient period capability [NR_RF_FR1] | |
| R4-2000442 | Feasibility of on-to-on transient period measurement in FR1 | Anritsu Corporation |
| R4-2001757 | On transient period UE capability | Huawei, HiSilicon |
| R4-2002096 | Summarizing the testability of transient capability reporting feature | Qualcomm Incorporated, Skyworks Solutions Inc., Verizon, Dish Network, Ericsson, CMCC, Keysight Technologies, Nokia, Nokia Shanghai Bell, Sprint, AT |
| R4-2002143 | EVM Measurements for FR1 Transient Period Capability Testability | Skyworks Solutions Inc. |
| 8.13.2 | RRM core requirements (38.133) [NR_RF_FR1] | |
| R4-2002183 | Email discussion summary for RAN4#94e_#60_NR_RF_FR1_RRM | Moderator (Huawei, HiSilicon) |
| R4-2002243 | WF on RRM requirements for Tx switching between two uplink carriers | Huawei, HiSilicon |
| R4-2002314 | Email discussion summary for RAN4#94e_#60_NR_RF_FR1_RRM | Moderator (Huawei, HiSilicon) |
| 8.13.2.1 | RRM requirements for Tx switching between two uplink carriers [NR_RF_FR1] | |
| R4-2000065 | Views on DL interruptions during UE switching between 1Tx carrier and 2Tx carrier | Huawei, HiSilicon |
| R4-2000068 | Draft LS to RAN1 on DL reception interruption due to switching between 1Tx carrier and 2Tx carrier | Huawei, HiSilicon |
| R4-2000135 | View on RRM interruption and delay requirement for switching between two uplink carriers | China Telecom |
| R4-2000457 | Interruption for Tx switching between two uplink carriers | MediaTek inc. |
| R4-2000640 | Discussion on DL interruption Tx switching between two uplink carriers | vivo |
| R4-2000793 | On RRM impact of Tx switching | Apple |
| R4-2000991 | On RRM requirements for Tx switching between two uplink carriers | OPPO |
| 8.14.1 | RF core requirements [NR_RF_FR2_req_enh] | |
| R4-2000021 | Multi-band requirement framework for FR2 in Rel-16 and beyond | Apple Inc. |
| R4-2000022 | [draft] LS response on Multiband relaxation for FR2 | Apple Inc. |
| R4-2000235 | Correction of the FR2 multi-band requirement framework | Apple Inc. |
| R4-2000236 | Correction of the FR2 multi-band requirement framework | Apple Inc. |
| R4-2002091 | Correction of Inner Allocation Definition for Powerclass 3 | Motorola Mobility España SA |
| R4-2002104 | Simplification of In-Band Emissions Requirements | Motorola Mobility España SA |
| 8.14.1.1 | FR2 MPE [NR_RF_FR2_req_enh] | |
| R4-2000006 | Further considerations on the uplink duty cycle enhancements for the MPE scenario | Apple Inc. |
| R4-2000114 | Further details on agreed signalling methods | Qualcomm Incorporated |
| R4-2000124 | Discussion on FR2 MPE mitigation | vivo |
| R4-2000197 | Remaining issues for MPE issues mitigation | InterDigital Communications |
| R4-2000318 | View on additional MPE enhancements | Samsung |
| R4-2000495 | Enhancement on FR2 MPE mitigation | ZTE Corporation |
| R4-2000955 | Rel-16 signaling solution - open issues | Intel Corporation |
| R4-2001198 | Discussion on enhancement of MPE in rel-16 on FR2 | LG Electronics France |
| R4-2001231 | Further on MPE enhancement | OPPO |
| R4-2001324 | P-MPR reporting for MPE enhancement | Ericsson, Sony |
| R4-2001382 | UE FR2 MPE enhancements and solutions | Nokia, Nokia Shanghai Bell |
| R4-2001383 | [Draft] LS on MPE enhancements | Nokia, Nokia Shanghai Bell |
| R4-2001781 | On MPE enhancement_FR2 | Huawei, HiSilicon |
| R4-2002693 | Email discussion summary for RAN4#94e_#20_NR_RF_FR2_req_enh_Part_1 | Moderator (OPPO) |
| R4-2002819 | WF on MPE solutions | OPPO |
| R4-2002820 | LS on the misalignment in P-bit between single entry and multi-entry PHR | RAN4 |
| R4-2002821 | [Draft] LS on MPE enhancements | Nokia, Nokia Shanghai Bell |
| R4-2002889 | Email discussion summary for RAN4#94e_#20_NR_RF_FR2_req_enh_Part_1 | Moderator (OPPO) |
| R4-2002916 | [Draft] LS on MPE enhancements | RAN4 |
| 8.14.1.2 | Beam Correspondence based on configured DL RS (SSB or CSI-RS) [NR_RF_FR2_req_enh] | |
| R4-2000012 | Remaining issues with beam correspondence in Rel-16 | Apple Inc. |
| R4-2000077 | FR2 Beam Correspondence using SSB only | Qualcomm Incorporated |
| R4-2000078 | Beam management CSI-RS design for BC requirement | Qualcomm Incorporated |
| R4-2000079 | Further enhancement of Beam Correspondence | Qualcomm Incorporated |
| R4-2000199 | On FR2 Initial access beam correspondence | Qualcomm Incorporated |
| R4-2000271 | Discussion on beam correspondence in Rel-16 | Samsung |
| R4-2000394 | SSB based Beam Correspondence | Intel Corporation |
| R4-2000791 | On SSB based beam correspondence | Apple |
| R4-2000858 | Views on beam correspondence enhancement based on SSB in Rel-16 | NTT DOCOMO, INC. |
| R4-2001065 | On the effect of beamforming with CA on beam correspondence | Fraunhofer HHI |
| R4-2001199 | Discussion on enhancement of BC in rel-16 at FR2 | LG Electronics France |
| R4-2001232 | Environmental condition based beam correspondence enhancement | OPPO |
| R4-2001325 | Test configuration and requirements for beam correspondence during initital access | Ericsson, Sony |
| R4-2001384 | FR2 Beam Correspondence enhancements | Nokia, Nokia Shanghai Bell |
| R4-2001490 | Views on SSB only and CSI-RS only beam correspondence | Sony, Ericsson |
| R4-2001493 | Enhanced reporting for beam correspondence in poor SNR condition | Sony |
| R4-2001761 | On beam correspondence enhancement | Huawei, HiSilicon |
| R4-2001777 | TP for beam correspondence based on CSI-RS only | Huawei, HiSilicon |
| R4-2002694 | Email discussion summary for RAN4#94e_#21_NR_RF_FR2_req_enh_Part_2 | Moderator (Apple) |
| R4-2002822 | WF on remaining issues with Rel-16 beam correspondence | Apple |
| R4-2002890 | Email discussion summary for RAN4#94e_#21_NR_RF_FR2_req_enh_Part_2 | Moderator (Apple) |
| 8.14.1.3 | Intra-band cont DL CA for aggregated BW larger than 1400 MHz [NR_RF_FR2_req_enh] | |
| R4-2000756 | FR2 CA bandwidth classes for aggregated channel BW > 1200 MHz | MediaTek Inc. |
| R4-2002695 | Email discussion summary for RAN4#94e_#22_NR_RF_FR2_req_enh_Part_3 | Moderator (Qualcomm) |
| R4-2002823 | WF on Intra-band contiguous DL CA | MediaTek |
| R4-2002824 | WF on Intra-band non-contiguous DL CA | Qualcomm |
| R4-2002825 | WF on Inter-band DL CA | Apple |
| R4-2002891 | Email discussion summary for RAN4#94e_#22_NR_RF_FR2_req_enh_Part_3 | Moderator (Qualcomm) |
| R4-2002920 | Email discussion summary for RAN4#94e_#22_NR_RF_FR2_req_enh_Part_3 | Moderator (Qualcomm) |
| 8.14.1.4 | Intra-band non-cont DL CA for aggregated BW larger than 1400 MHz [NR_RF_FR2_req_enh] | |
| R4-2000013 | Remaining issues with the FR2 frequency separation class | Apple Inc. |
| R4-2000014 | CR to 38.101-2 on FR2 frequency separation class enhancement | Apple Inc. |
| R4-2000015 | Views on FR2 DL intra-band CA REFSENS | Apple Inc. |
| R4-2000207 | FR2 DL Intra-band CA BW Enhancement Feature Parameters | Qualcomm Incorporated |
| R4-2000208 | TP to TR38.831: FR2 UE architectures for DL Intra-band CA BW Enhancement | Qualcomm Incorporated |
| R4-2000209 | LS on FR2 DL Intra-band CA BW Enhancement Feature Parameters | Qualcomm Incorporated |
| R4-2000210 | FR2 enhanced DL BW definitions | Qualcomm Incorporated |
| R4-2000211 | Draft CR to 38.101-2: DL CA BW Enhancement for Rel-16 | Qualcomm Incorporated |
| R4-2000759 | On FR2 DL intra-band CA cumulative aggregated BW enhancement | MediaTek Inc. |
| R4-2001760 | On intra-band NC DL CA_FR2 | Huawei, HiSilicon |
| 8.14.1.5 | Intra-band contiguous UL CA [NR_RF_FR2_req_enh] | |
| R4-2002696 | Email discussion summary for RAN4#94e_#23_NR_RF_FR2_req_enh_Part_4 | Moderator (Nokia) |
| R4-2002826 | WF on radiative degradation mechanisms for larger frequency separation | Qualcomm |
| R4-2002827 | WF on FR2 ACLR MBW | Skyworks |
| R4-2002828 | WF on multiband relaxation framework | Sony, OPPO |
| R4-2002892 | Email discussion summary for RAN4#94e_#23_NR_RF_FR2_req_enh_Part_4 | Moderator (Nokia) |
| 8.14.1.6 | Intra-band non-contiguous UL CA [NR_RF_FR2_req_enh] | |
| R4-2000019 | Non-simultaneous UL for non-contiguous UL CA in FR2 | Apple Inc. |
| R4-2000509 | FR2 nc-in-ca MPR | Nokia, Nokia Shanghai Bell |
| R4-2000693 | On using Rel-15 CA MPR table format for FR2 NC UL CA | Qualcomm Incorporated |
| R4-2000694 | dCR to 38.101-2: Simultaneous NC UL CA framework for Rel-16 | Qualcomm Incorporated |
| R4-2002147 | Beam squint analysis for FR2 PC3 UEs | Qualcomm Incorporated |
| 8.14.1.7 | Inter-band DL CA [NR_RF_FR2_req_enh] | |
| R4-2000016 | Remaining issues with FR2 inter-band CA | Apple Inc. |
| R4-2000017 | Views on FR2 DL inter-band CA REFSENS | Apple Inc. |
| R4-2000018 | EIS spherical coverage for inter-band CA in FR2 | Apple Inc. |
| R4-2000115 | Inter-band CA remaining open requirements | Qualcomm Incorporated |
| R4-2000116 | draftCR: Introduction of inter-band CA to 38.101-2 | Qualcomm Incorporated |
| R4-2000357 | Inter-band CA with/without independent Rx beam | Qualcomm Incorporated |
| R4-2000395 | PSD imbalance in Inter-band DL CA | Intel Corporation |
| R4-2000443 | Test system for inter-band DL CA in FR2 | Anritsu Corporation |
| R4-2000444 | Consideration on two-DL spherical coverage test with power imbalance | Anritsu Corporation |
| R4-2000445 | Consideration on capability of multi signal transmission from single AoA in FR2 OTA test system | Anritsu Corporation |
| R4-2000446 | Influences of multiple offset antennas in FR2 chamber | Anritsu Corporation |
| R4-2000796 | FR2 inter-band DL CA relaxation framework | MediaTek Beijing Inc. |
| R4-2001044 | Discussion on FR2 intra-band DL CA enhancement | Nokia, Nokia Shanghai Bell |
| R4-2001494 | Views spherical coverage relaxation for inter band DL CA | Sony, Ericsson |
| R4-2001776 | On inter band DL CA_FR2 | Huawei, HiSilicon |
| R4-2001779 | TP for inter-band CA refsens FR2_Rel-16 | Huawei, HiSilicon |
| R4-2002114 | PSD imbalance for FR2 Inter-band DL CA of 28GHz + 40GHz | NTT DOCOMO INC. |
| 8.14.1.8 | Improvement of UE MPR [NR_RF_FR2_req_enh] | |
| R4-2000396 | FR2 CA MPR improvement | Intel Corporation |
| R4-2000518 | FR2 boosting | Nokia, Nokia Shanghai Bell |
| 8.14.1.9 | Improvement of spherical coverage requirements for PC3 [NR_RF_FR2_req_enh] | |
| R4-2000020 | Views on PC3 spherical coverage requirements in Rel-16 and beyond | Apple Inc. |
| R4-2000317 | View on spherical coverage improvement for Rel-16 | Samsung |
| R4-2000750 | Views on spherical coverage enhancement for PC3 | vivo |
| R4-2000956 | Views on potential spherical coverage enhancements | Intel Corporation |
| R4-2001233 | About spherical coverage enhancement | OPPO |
| R4-2001234 | About multi-band relaxation tests | OPPO |
| R4-2001495 | Views on improvement to spherical coverage requirements for PC3 | Sony |
| R4-2002113 | Further discussion on Spherical coverage enhancement | NTT DOCOMO INC. |
| R4-2002697 | Email discussion summary for RAN4#94e_#24_NR_RF_FR2_req_enh_Part_5 | Moderator (Samsung) |
| R4-2002829 | WF on spherical coverage improvements | Samsung |
| R4-2002893 | Email discussion summary for RAN4#94e_#24_NR_RF_FR2_req_enh_Part_5 | Moderator (Samsung) |
| 8.14.2 | RRM core requirements (38.133) [NR_RF_FR2_req_enh] | |
| R4-2002184 | Email discussion summary for RAN4#94e_#61_NR_RF_FR2_req_enh_RRM | Moderator (Apple) |
| R4-2002279 | WF on RRM requirements for FR2 inter-band DL CA | Apple |
| R4-2002315 | Email discussion summary for RAN4#94e_#61_NR_RF_FR2_req_enh_RRM | Moderator (Apple) |
| 8.14.2.1 | Inter-band DL CA MRTD [NR_RF_FR2_req_enh] | |
| R4-2000456 | MRTD requirements for FR2 inter-band DL CA | MediaTek inc. |
| R4-2000786 | On MRTD requirement for FR2 inter-band CA | Apple |
| R4-2001581 | Discussion on MRTD requirements for FR2 inter-band DL CA | Huawei, HiSilicon |
| 8.15.1 | RRM core requirements (38.133) [NR_RRM_Enh_Core] | |
| R4-2002185 | Email discussion summary for RAN4#94e_#62_NR_RRM_Enh_RRM_Part_1 | Moderator (Intel Corporation) |
| R4-2002186 | Email discussion summary for RAN4#94e_#63_NR_RRM_Enh_RRM_Part_2 | Moderator (ZTE) |
| R4-2002187 | Email discussion summary for RAN4#94e_#64_NR_RRM_Enh_RRM_Part_3 | Moderator (Apple) |
| R4-2002189 | Email discussion summary for RAN4#94e_#66_NR_CSIRS_L3meas_RRM_Part_2 | Moderator (OPPO) |
| R4-2002244 | WF on R16 NR RRM enhancements - BWP switching on multiple CCs | Intel |
| R4-2002245 | WF on R16 NR RRM enhancements - WF on UL spatial relation info switching | MediaTek |
| R4-2002246 | WF on R16 NR RRM enhancements – SRS carrier switching | ZTE |
| R4-2002247 | WF on R16 NR RRM enhancements – CGI reading | ZTE |
| R4-2002248 | WF on R16 NR RRM enhancements – Mandatory MG patterns | ZTE |
| R4-2002249 | WF on R16 NR RRM enhancements – Multiple Scell activation/deactivation and UE-specific CBW change | Apple |
| R4-2002250 | WF on R16 NR RRM enhancements – Inter-frequency measurement without MG | CMCC |
| R4-2002251 | WF on R16 NR RRM enhancements – FR2 inter-band CA requirement | Huawei |
| R4-2002316 | Email discussion summary for RAN4#94e_#62_NR_RRM_Enh_RRM_Part_1 | Moderator (Intel Corporation) |
| R4-2002317 | Email discussion summary for RAN4#94e_#63_NR_RRM_Enh_RRM_Part_2 | Moderator (ZTE) |
| R4-2002318 | Email discussion summary for RAN4#94e_#64_NR_RRM_Enh_RRM_Part_3 | Moderator (Apple) |
| R4-2002329 | WF on R16 NR RRM enhancements | ZTE |
| 8.15.1.1 | SRS carrier switching requirements [NR_RRM_Enh_Core] | |
| R4-2000658 | Interruption requirements due to SRS carrier switching | Nokia, Nokia Shanghai Bell |
| R4-2001033 | Discussion on Interruption at SRS carrier switch | MediaTek inc. |
| R4-2001267 | CR to 38.133 on SRS carrier switching interruption requirements | ZTE |
| R4-2001268 | CR to 36.133 on SRS carrier switching interruption requirements | ZTE |
| R4-2001275 | Further discussion on SRS carrier switching RRM requirements | ZTE |
| R4-2001661 | Discussion on SRS carrier switching interruption | Huawei, HiSilicon |
| R4-2001662 | CR on NR SRS carrier switching interruption in TS 36.133 | Huawei, HiSilicon |
| R4-2002058 | Discussion on remaining issues in SRS carrier switching | Qualcomm Incorporated |
| 8.15.1.2 | Multiple Scell activation/deactivation [NR_RRM_Enh_Core] | |
| R4-2000785 | On remaining issues for activation delay extension due to multiple SCell | Apple |
| R4-2001012 | On remaining open issues in delay extension of multiple SCell activation | NEC |
| R4-2001034 | Discussion on Multiple SCell activation | MediaTek inc. |
| R4-2001641 | Discussion on multiple SCell activation | Huawei, HiSilicon |
| R4-2002061 | Discussion on Multiple SCell activation in NR | Qualcomm Incorporated |
| R4-2002089 | On activation of multiple SCells | Ericsson |
| 8.15.1.3 | CGI reading requirements with autonomous gap [NR_RRM_Enh_Core] | |
| R4-2001035 | Discussion on CGI reading requirement for NR | MediaTek inc. |
| R4-2001263 | CR to 38.133 on CGI reading of NR cell | ZTE |
| R4-2001264 | CR to 38.133 on interruption requirements for CGI reading | ZTE |
| R4-2001271 | Updated simulation assumption on SIB1 decoding for NR CGI reading | ZTE |
| R4-2001272 | Simulation results of SIB1 decoding for NR CGI reading | ZTE |
| R4-2001273 | Further discussion on NR CGI reading with autonomous gaps | ZTE |
| R4-2001364 | PDSCH simulation result for SI reading | Ericsson |
| R4-2001403 | Further considerations on CGI reading for NR | Ericsson |
| R4-2001404 | LTE CGI measurements with autonomous gaps for 36.133 | Ericsson |
| R4-2001405 | NR CGI measurements with autonomous gaps for 38.133 | Ericsson |
| R4-2001642 | Discussion on NR CGI reading requirements | Huawei, HiSilicon |
| R4-2001643 | Simulation results for SIB1 decoding in CGI requirements | Huawei, HiSilicon |
| R4-2001644 | Discussion on LTE CGI reading requirements | Huawei, HiSilicon |
| R4-2001645 | CR to 36.133 on interruption requirements for CGI reading | Huawei, HiSilicon |
| R4-2001646 | CR to 36.133 on CGI reading of LTE cell | Huawei, HiSilicon |
| R4-2002046 | discussion on CGI reading with autonomous gap | Nokia, Nokia Shanghai Bell |
| R4-2002053 | Discussion on interruption requirements for autonomous gaps for CGI reading | Qualcomm Incorporated |
| 8.15.1.4 | BWP switching on multiple CCs [NR_RRM_Enh_Core] | |
| R4-2000155 | BWP switching delay requirement on multiple CCs | vivo |
| R4-2000156 | Interruption time of BWP switching delay on multiple CCs | vivo |
| R4-2000372 | RRM requirements for BWP switching on multiple CCs | Intel Corporation |
| R4-2000459 | Discussion on BWP requirements for multiple CCs | MediaTek inc. |
| R4-2001013 | Requirements for BWP switch delay on multiple CC | NEC |
| R4-2001548 | Discussion on BWP switching on multiple CCs | Huawei, HiSilicon |
| R4-2001851 | Analysis of partially overlapped BWP triggering on multiple CCs | Ericsson |
| R4-2002047 | discussion on Interruption requirements with BWP switch on multiple CCs | Nokia, Nokia Shanghai Bell |
| R4-2002054 | Discussion on timeline for BWP switch for multiple cells | Qualcomm Incorporated |
| R4-2002090 | On simultaneously triggered BWP switching on multiple CCs | Ericsson |
| 8.15.1.5 | Inter-frequency measurement requirement without MG [NR_RRM_Enh_Core] | |
| R4-2000154 | Remaining issues on inter-frequency measurement without gap | vivo |
| R4-2000385 | Discussion about inter-frequency measurement without gap | Intel Corporation |
| R4-2000460 | Inter-frequency measurement requirement without gap | MediaTek inc. |
| R4-2000644 | RRM requirements on inter-frequency measurement without gap | CMCC |
| R4-2000645 | TP on introducing inter-frequency measurements without measurement gap | CMCC |
| R4-2000646 | LS on inter-frequency measurement without gap | CMCC |
| R4-2000992 | Further discussion on inter-frequency measurement requirement | OPPO |
| R4-2001663 | [Draft] LS on inter-frequency measurement requirement without MG | Huawei, HiSilicon |
| R4-2001664 | Discussion on inter-frequency without gap | Huawei, HiSilicon |
| R4-2002057 | Discussion on inter-frequency measurements without gaps | Qualcomm Incorporated |
| 8.15.1.6 | Mandatory MG patterns [NR_RRM_Enh_Core] | |
| R4-2000561 | Discussion on mandatory MG patterns for FR2 | NTT DOCOMO INC. |
| R4-2000638 | Further discussion on mandating gap patterns for Rel-16 NR | CMCC |
| R4-2000993 | Discussion on mandatory measurement gap patterns and applicability | OPPO |
| R4-2001269 | LS on mandatory of measurement gap patterns | ZTE |
| R4-2001274 | Further discussion on mandatary of measurement gap patterns | ZTE |
| R4-2001345 | Discussion on Mandatory GPs for NR Rel-16 | Nokia, Nokia Shanghai Bell |
| R4-2001400 | Considerations on mandatory gap patterns for NR only measurements in release 16 | Ericsson |
| R4-2001401 | Mandatory gap patterns in NR RRM enhancement | Ericsson |
| R4-2001402 | LS on mandatory gap patterns for release 16 | Ericsson |
| R4-2001665 | Discussion on mandatory gap pattern in R-16 | Huawei, HiSilicon |
| R4-2001666 | LS on mandatory gap patterns in R16 | Huawei, HiSilicon |
| R4-2001799 | Discussion on mandatory MG patterns in Rel-16 | MediaTek inc. |
| R4-2001800 | LS on new capability for NR measurement and mandatory MG patterns in Rel-16 | MediaTek inc. |
| R4-2002063 | Further discussion on mandatory measurement gaps | Qualcomm Incorporated |
| R4-2002252 | LS on mandatory of measurement gap patterns | ZTE |
| 8.15.1.7 | UE-specific CBW change [NR_RRM_Enh_Core] | |
| R4-2000461 | Delay requirement for UE-specific channel bandwidth change | MediaTek inc. |
| R4-2002065 | Discussion on UE specific channel BW change | Qualcomm Incorporated |
| 8.15.1.8 | Spatial relation switch for uplink [NR_RRM_Enh_Core] | |
| R4-2000373 | Discussion on requirements for spatial relation info switch for uplink | Intel Corporation |
| R4-2001036 | Discussion on active spatial relation switch | MediaTek inc. |
| R4-2001667 | Discussion on spatial relation switch for uplink channels and SRS | Huawei, HiSilicon |
| R4-2002060 | Discussion on requirements for spatial relation switch | Qualcomm Incorporated |
| R4-2002088 | On spatial relation switching delay requirements | Ericsson |
| 8.15.1.9 | Non-simultaneous UL carrier operation in FR2 [NR_RRM_Enh_Core] | |
| R4-2002163 | On RRM impact of Non-simultaneous UL for non-contiguous UL CA in FR2 | Apple Inc. |
| 8.15.1.10 | Inter-band CA requirement for FR2 UE measurement capability of independent Rx beam and/or common beam [NR_RRM_Enh_Core] | |
| R4-2000381 | RRM impact on inter-band CA in FR2 | Intel Corporation |
| R4-2000560 | Discussion on inter-band CA requirement for FR2 | NTT DOCOMO INC. |
| R4-2001582 | Discussion on RRM impacts of FR2 inter-band CA | Huawei, HiSilicon |
| R4-2002064 | RRM requirements with common and independent beams in FR2 | Qualcomm Incorporated |
| 8.16.1 | RRM core requirements (38.133) [NR_CSIRS_L3meas-Core] | |
| R4-2002188 | Email discussion summary for RAN4#94e_#65_NR_CSIRS_L3meas_RRM_Part_1 | Moderator (CATT) |
| R4-2002199 | Email discussion summary for RAN4#94e_#66_NR_CSIRS_L3meas_RRM_Part_2 | Moderator (OPPO) |
| R4-2002257 | WF on CSI-RS configuration and intra/inter-frequency measurements definition for CSI-RS based L3 measurement | CATT |
| R4-2002258 | WF on CSI-RS based L3 measurement capability and requirements | OPPO |
| R4-2002319 | Email discussion summary for RAN4#94e_#65_NR_CSIRS_L3meas_RRM_Part_1 | Moderator (CATT) |
| R4-2002320 | Email discussion summary for RAN4#94e_#66_NR_CSIRS_L3meas_RRM_Part_2 | Moderator (OPPO) |
| 8.16.1.1 | CSI-RS measurement bandwidth [NR_CSIRS_L3meas-Core] | |
| R4-2000386 | Discussion about CSI-RS L3 measurement bandwidth | Intel Corporation |
| R4-2000462 | Simulation results for CSI-RS measurement BW | MediaTek inc. |
| R4-2000582 | Further discussion on CSI-RS measurement configuration for RRM measurement requirement | CATT |
| R4-2000636 | Discussion on CSI-RS measurement bandwidth | CMCC |
| R4-2000655 | Discussion on CSI-RS measurement bandwidth | Nokia, Nokia Shanghai Bell |
| R4-2000945 | Discussion on CSI-RS parameters on RRM core requirements | NTT DOCOMO, INC. |
| R4-2001583 | Further discussion on CSI-RS based L3 measurement requirements | Huawei, HiSilicon |
| 8.16.1.2 | CSI-RS based intra-frequency and inter-frequency measurements definition [NR_CSIRS_L3meas-Core] | |
| R4-2000387 | Discussion about CSI-RS L3 measurement definition | Intel Corporation |
| R4-2000463 | Definition of Intra and inter frequency for CSI-RS RRM | MediaTek inc. |
| R4-2000583 | Further discussion on definition of CSI-RS based intra-frequency and inter-frequency measurement | CATT |
| R4-2000584 | LS on CSI-RS based intra-frequency and inter-frequency Measurement definition | CATT |
| R4-2000637 | Discussion on CSI-RS based intra-frequency measurements definition | CMCC |
| R4-2000656 | CSI-RS based intra-f and inter-f measurement definition | Nokia, Nokia Shanghai Bell |
| R4-2000792 | On the definition of CSI-RS based intra-frequency and inter-frequency layers | Apple |
| R4-2000946 | Definition of intra-frequency measurement for CSI-RS based L3 measurement | NTT DOCOMO, INC. |
| R4-2000994 | On definition of CSI-RS based intra-frequency and inter-frequency measurements | OPPO |
| R4-2001014 | Definition of Intra and Inter-frequency CSI-RS based L3 measurements | NEC |
| R4-2001277 | Further discussion on definition of CSI-RS based RRM measurements | ZTE |
| R4-2001656 | Definition for the CSI-RS based intra-frequency and inter-frequency measurement | Huawei, HiSilicon |
| R4-2001657 | [DRAFT] Reply LS on clarification about CSI-RS measurement | Huawei, HiSilicon |
| R4-2002055 | Discussion on definition for intra and inter-frequency for CSI-RS based RRM measurements | Qualcomm Incorporated |
| 8.16.1.3 | Measurement capability [NR_CSIRS_L3meas-Core] | |
| R4-2000464 | Discussion on measurement capability for CSI-RS RRM | MediaTek inc. |
| R4-2000585 | Further discussion on CSI-RS based UE measurement capabilities | CATT |
| R4-2000995 | On Measurement capability for CSI-RS L3 measurement | OPPO |
| R4-2001276 | Further discussion on UE measurement capability of CSI-RS based RRM measurements | ZTE |
| R4-2001647 | On synchronization assumption for CSI-RS measurement requirements | Huawei, HiSilicon |
| 8.16.1.4 | Intra-frequency measurement requirements [NR_CSIRS_L3meas-Core] | |
| R4-2000465 | Cell identification requirements for CSI-RS RRM | MediaTek inc. |
| R4-2000586 | Discussion on CSI-RS based measurement requirements | CATT |
| R4-2000947 | QCL assumptions for CSI-RS based L3 measurement | NTT DOCOMO, INC. |
| R4-2000996 | On measurement requirement for CSI-RS based L3 measurements | OPPO |
| R4-2001658 | Discussion on CSI-RS based L3 measurement requirements and scheduling restriction | Huawei, HiSilicon |
| 8.16.1.6 | Others [NR_CSIRS_L3meas-Core] | |
| R4-2000466 | Discussion on pre-emption on CSI-RS for L3 measurement | MediaTek inc. |
| R4-2000467 | Draft LS on pre-emption on CSI-RS for L3 measurement | MediaTek inc. |
| R4-2000657 | Simulation results for CSI-RS based measurements | Nokia, Nokia Shanghai Bell |
| R4-2001648 | On CSI-RS measurement capability | Huawei, HiSilicon |
| 8.17.1 | RRM core requirements (38.133) [NR_HST-Core] | |
| R4-2000572 | Further discussion on RRM requirements in NR HST scenarios | CATT |
| R4-2000632 | Discussion on RRM for NR high speed scenario | CMCC |
| R4-2000772 | On NR HST RRM Requirements | Qualcomm, Inc. |
| R4-2001346 | System simulation results and RRM Requirements NR HST | Nokia, Nokia Shanghai Bell |
| R4-2001389 | Considerations on high speed requirements for NR | Ericsson |
| R4-2001659 | Discussion on the RRM requirements in NR HST | Huawei, HiSilicon |
| R4-2002190 | Email discussion summary for RAN4#94e_#67_NR_HST_RRM | Moderator (CMCC) |
| R4-2002253 | WF on NR HST RRM requirements | CMCC |
| R4-2002321 | Email discussion summary for RAN4#94e_#67_NR_HST_RRM | Moderator (CMCC) |
| 8.17.1.1 | Cell re-selection [NR_HST-Core] | |
| R4-2000573 | CR on cell re-selection requirements for NR HST | CATT |
| R4-2000639 | 38.133 CR on cell re-selection requirements for Rel-16 NR HST | CMCC |
| R4-2001390 | TP:High speed enhancements for NR idle mode | Ericsson |
| 8.17.1.2 | Cell identification delay [NR_HST-Core] | |
| R4-2000159 | Discussion on cell identification delay for connected mode UE in NR HST | vivo |
| R4-2000574 | CR on cell identification requirements for NR HST | CATT |
| R4-2000859 | Cell identification delay requirements for DRX case in HST scenario | NTT DOCOMO, INC. |
| R4-2001391 | TP:High speed enhancements for NR RRC connected mode | Ericsson |
| R4-2001660 | Discussion on SS-SINR in NR HST | Huawei, HiSilicon |
| 8.17.1.3 | RLM [NR_HST-Core] | |
| R4-2001355 | RLM for NR HST | Ericsson |
| 8.17.1.4 | Beam management [NR_HST-Core] | |
| R4-2001356 | Beam management for high speed train scenario | Ericsson |
| R4-2001721 | L1-RSRP measurement accuracy and delay for Rel-16 high speed train | Nokia, Nokia Shanghai Bell |
| 8.17.1.5 | Inter-RAT measurement [NR_HST-Core] | |
| R4-2000160 | Discussion on inter-RAT measurment requirements in NR HST | vivo |
| R4-2000631 | Discussion on inter-RAT measurement requirements for NR HST | CMCC |
| R4-2001392 | TP: interRAT NR high speed updates in 36.133 | Ericsson |
| 8.17.2 | Demodulation and CSI requirements (38.101-4 / 38.104) [NR_HST-Perf] | |
| R4-2002384 | Email discussion summary for RAN4#94e_#93_NR_HST_Demod_UE | Moderator (China Mobile) |
| R4-2002385 | Email discussion summary for RAN4#94e_#94_NR_HST_Demod_BS | Moderator (Nokia) |
| R4-2002405 | WF on Rel-16 NR HST BS demodulation requirements scenario | Nokia, Nokia Shanghai Bell |
| R4-2002418 | WF on Rel-16 NR HST UE demodulation | CMCC |
| R4-2002522 | Email discussion summary for RAN4#94e_#93_NR_HST_Demod_UE | Moderator (China Mobile) |
| R4-2002523 | Email discussion summary for RAN4#94e_#94_NR_HST_Demod_BS | Moderator (Nokia) |
| 8.17.2.1 | UE demodulation and CSI requirements (38.101-4) [NR_HST-Perf] | |
| R4-2000634 | Further discussion on UE demodulation for NR support of high speed scenario | CMCC |
| R4-2000948 | Release independent applicability for HST requirements | NTT DOCOMO, INC. |
| R4-2002072 | Views on Tests for High Speed Train Scenarios | Qualcomm Incorporated |
| 8.17.2.1.1 | Scenarios and transmission schemes [NR_HST-Perf] | |
| R4-2000366 | Views on DL demodulation requirements for different transmission schemes in NR HST-SFN | Intel Corporation |
| R4-2001357 | Transmission scheme in NR PDSCH demodulation requirements for HST | Ericsson |
| R4-2001454 | Discussion on transmission schemes for NR HST UE demodulation requirements | Huawei, HiSilicon |
| 8.17.2.1.2 | Requirements for HST-SFN [NR_HST-Perf] | |
| R4-2000303 | Simulation results for UE demodulation requirements under HST single tap | Samsung |
| R4-2000367 | Views on NR UE demodulation requirements for HST-SFN scenario with JT operation | Intel Corporation |
| R4-2000949 | Views on HST-SFN for NR | NTT DOCOMO, INC. |
| R4-2001497 | Discussion and simulation results on NR UE HST performance requirements under SFN | Huawei, HiSilicon |
| 8.17.2.1.3 | Requirements for HST single tap [NR_HST-Perf] | |
| R4-2000304 | Simulation results for UE demodulation requirements under HST SFN | Samsung |
| R4-2000368 | Views on NR UE demodulation requirements for HST single tap scenario | Intel Corporation |
| R4-2000950 | Views on HST single tap for NR | NTT DOCOMO, INC. |
| R4-2001358 | Discussion on PDSCH demodulation performance with HST single tap | Ericsson |
| R4-2001455 | Discussion and simulation results on NR UE HST performance requirements under single-tap | Huawei, HiSilicon |
| R4-2001736 | Simulation results for NR UE HST single tap | Ericsson |
| 8.17.2.1.4 | Requirements for multi-path fading channels [NR_HST-Perf] | |
| R4-2000305 | Simulation results for UE demodulation requirements under fading channel with high Doppler value | Samsung |
| R4-2000369 | Views on NR UE demodulation requirements for HST scenario with fading channel conditions | Intel Corporation |
| R4-2000951 | Views on High-speed multi-path fading channels | NTT DOCOMO, INC. |
| R4-2001456 | Discussion and simulation results on NR UE HST performance requirements under multi-path fading channel | Huawei, HiSilicon |
| R4-2001737 | Simulation results for HST Multipath fading channels | Ericsson |
| 8.17.2.1.5 | Network assistance and UE capability signalling [NR_HST-Perf] | |
| R4-2001457 | Discussion on the requirement definition for NR UE HST single tap channel | Huawei, HiSilicon |
| 8.17.2.2 | BS demodulation requirements (38.104) [NR_HST-Perf] | |
| R4-2000613 | Summary of ideal and impairment results for NR HST demodulation requirements | CATT |
| R4-2001687 | NR Rel-16 HST BS demodulation PUSCH and UL TA simulation results | Nokia, Nokia Shanghai Bell |
| R4-2001689 | On NR Rel-16 HST BS demodulation PUSCH and UL TA requirements | Nokia, Nokia Shanghai Bell |
| R4-2002417 | Summary of ideal and impairment results for NR HST demodulation requirements | CATT |
| 8.17.2.2.1 | PUSCH requirements [NR_HST-Perf] | |
| R4-2000306 | Discussion and initial simulation results for NR HST PUSCH | Samsung |
| R4-2000404 | Simulation results for Rel-16 NR HST PUSCH demodulation performance at UE speed of 350 km/h | Ericsson |
| R4-2000405 | Simulation results for Rel-16 NR HST PUSCH demodulation performance at UE speed of 500 km/h | Ericsson |
| R4-2000608 | Discussion on Front loaded DMRS start symbol for NR HST PUSCH | CATT |
| R4-2000609 | Discussion on antenna configuration and MCS for NR HST PUSCH | CATT |
| R4-2000610 | Initial simulation results for NR HST PUSCH demodulation requirement | CATT |
| R4-2000633 | Simulation results on PUSCH for NR support of high speed scenario | CMCC |
| R4-2000807 | Simulation results for NR HST PUSCH | ZTE Wistron Telecom AB |
| R4-2001184 | Introducting of conformance tests for 350km/h HST | Ericsson |
| R4-2001185 | Introduction of HST 350km/h FRCs and channel model | Ericsson |
| R4-2001195 | Views on NR PUSCH for high speed | NTT DOCOMO, INC. |
| R4-2001458 | Discussion on NR HST PUSCH performance requirements | Huawei, HiSilicon |
| R4-2001459 | Simulation results on NR HST PUSCH performance requirements | Huawei, HiSilicon |
| R4-2001690 | CR for 38.104: HST PUSCH demodulation requirements introduction | Nokia, Nokia Shanghai Bell |
| R4-2001691 | CR for 38.104: HST PUSCH demodulation Annex including both FRC and channel model | Nokia, Nokia Shanghai Bell |
| R4-2001802 | CR for TS 38.141-1: Introduction of NR PUSCH performance requirements for HST | NTT DOCOMO, INC. |
| R4-2001803 | CR for TS 38.141-1: Introduction of NR PUSCH performance Annex including both FRC and channel model for HST | NTT DOCOMO, INC. |
| R4-2002406 | CR for 38.104: HST PUSCH demodulation requirements introduction | Nokia, Nokia Shanghai Bell |
| R4-2002407 | CR for 38.104: HST PUSCH demodulation Annex including both FRC and channel model | Nokia, Nokia Shanghai Bell |
| R4-2002408 | CR for TS 38.141-1: Introduction of NR PUSCH performance requirements for HST | NTT DOCOMO, INC. |
| R4-2002409 | CR for TS 38.141-1: Introduction of NR PUSCH performance Annex including both FRC and channel model for HST | NTT DOCOMO, INC. |
| R4-2002415 | Introducting of conformance tests for 350km/h HST | Ericsson |
| R4-2002416 | Introduction of HST 350km/h FRCs and channel model | Ericsson |
| R4-2002536 | CR for 38.104: HST PUSCH demodulation requirements introduction | Nokia, Nokia Shanghai Bell |
| R4-2002537 | CR for 38.104: HST PUSCH demodulation Annex including both FRC and channel model | Nokia, Nokia Shanghai Bell |
| 8.17.2.2.2 | PRACH requirements [NR_HST-Perf] | |
| R4-2000307 | Ideal and impairment simulation results for NR HST PRACH | Samsung |
| R4-2000407 | Simulation results for PRACH HST with 350km/h | Ericsson |
| R4-2000408 | Simulation results for PRACH HST with 500km/h | Ericsson |
| R4-2000611 | Initial simulation results for NR HST PRACH demodulation requirement with PRACH format 0 | CATT |
| R4-2000612 | Initial simulation results for NR HST PRACH demodulation requirement with PRACH short sequence format | CATT |
| R4-2000809 | Simulation results for NR HST PRACH | ZTE Wistron Telecom AB |
| R4-2001471 | Ideal and impairment simulation results for NR HST PRACH format 0 | Huawei, HiSilicon |
| R4-2001472 | Ideal and impairment simulation results for NR HST PRACH short sequence format | Huawei, HiSilicon |
| R4-2001473 | CR for TS 38.104: Introduction of PRACH demodulation requirements for NR HST | Huawei, HiSilicon |
| R4-2001474 | CR for TS 38.141-1: Introduction of PRACH performance requirements for NR HST | Huawei, HiSilicon |
| R4-2001475 | CR for TS 38.141-2: Introduction of PRACH performance requirements for NR HST | Huawei, HiSilicon |
| R4-2001688 | NR Rel-16 HST BS demodulation PRACH remaining issues and simulation results | Nokia, Nokia Shanghai Bell |
| R4-2002410 | CR for TS 38.104: Introduction of PRACH demodulation requirements for NR HST | Huawei, HiSilicon |
| R4-2002411 | CR for TS 38.141-1: Introduction of PRACH performance requirements for NR HST | Huawei, HiSilicon |
| R4-2002412 | CR for TS 38.141-2: Introduction of PRACH performance requirements for NR HST | Huawei, HiSilicon |
| 8.17.2.2.3 | UL timing adjustment requirements [NR_HST-Perf] | |
| R4-2000308 | Discussion and initial simulation results for NR UL timing adjustment | Samsung |
| R4-2000406 | Simulation results for Rel-16 NR PUSCH UL timing adjustment | Ericsson |
| R4-2000805 | CR for 38.104: introduction of UL timing adjustment | ZTE Wistron Telecom AB |
| R4-2000806 | CR for 38.104: Appendix for UL timing adjustment | ZTE Wistron Telecom AB |
| R4-2000808 | Simulation results for NR UL timing adjustment | ZTE Wistron Telecom AB |
| R4-2001460 | Discussion on the UL timing adjustment | Huawei, HiSilicon |
| R4-2002413 | CR for 38.104: introduction of UL timing adjustment | ZTE Wistron Telecom AB |
| R4-2002414 | CR for 38.104: Appendix for UL timing adjustment | ZTE Wistron Telecom AB |
| R4-2002538 | CR for 38.104: introduction of UL timing adjustment | ZTE Wistron Telecom AB |
| R4-2002539 | CR for 38.104: Appendix for UL timing adjustment | ZTE Wistron Telecom AB |
| 8.18 | NR performance requirement enhancement [NR_perf_enh-Perf] | |
| R4-2002386 | Email discussion summary for RAN4#94e_#95_NR_perf_enh_Demod | Moderator (China Telecomm) |
| R4-2002390 | Way forward on release independent aspect for UE demodulation and CSI reporting requirements | Huawei |
| R4-2002391 | Way forward on PDSCH CA normal demodulation requirementsWay forward on PDSCH CA normal demodulation requirements | Intel |
| R4-2002392 | Simulation assumptions for NR normal CA UE performance requirements | Intel |
| R4-2002393 | Way forward on PMI reporting requirements for Tx ports larger than 8 and up to 32 | Ericsson |
| R4-2002394 | Simulation assumptions for NR PMI reporting requirements for more than 8 Tx ports | Ericsson |
| R4-2002395 | Summary of simulation results for LTE-NR coexistence for TDD | Huawei, HiSilicon |
| R4-2002396 | Way forward on UE FR1 CA power imbalance requirements | NTT DoCoMo |
| R4-2002397 | Way forward on PUSCH demodulation requirements for 30% throughput throughput | NTT DoCoMo |
| R4-2002524 | Email discussion summary for RAN4#94e_#95_NR_perf_enh_Demod | Moderator (China Telecomm) |
| 8.18.1 | UE demodulation and CSI requirements (38.101-4) [NR_perf_enh-Perf] | |
| R4-2001445 | Discussion on release independence for NR Rel-16 enhanced UE demodulation requirements | Huawei, HiSilicon |
| 8.18.1.1 | NR CA PDSCH requirementS [NR_perf_enh-Perf] | |
| R4-2000136 | On NR CA PDSCH normal demodulation requirements | China Telecom |
| R4-2000137 | Initial simulation results for NR CA PDSCH normal demodulation requirements | China Telecom |
| R4-2000359 | Discussion on NR CA UE demodulation requirements | Intel Corporation |
| R4-2000360 | Simulation results for Normal CA requirements | Intel Corporation |
| R4-2000361 | Summary of Normal CA simulation results (FR1 15 kHz FDD and TDD) | Intel Corporation |
| R4-2000362 | Summary of Normal CA simulation results (FR1 30 kHz TDD) | Intel Corporation |
| R4-2000363 | Summary of Normal CA simulation results (FR2) | Intel Corporation |
| R4-2000647 | Discussion on NR CA PDSCH normal demodulation | CMCC |
| R4-2000952 | Views on normal PDSCH demodulation test for NR CA | NTT DOCOMO, INC. |
| R4-2001354 | Simulation result of NR PDSCH demodulation requirements with CA | Ericsson |
| R4-2001419 | Views on NR CA PDSCH Demodulation Performance Tests | Qualcomm Incorporated |
| R4-2001444 | Simulation Results for NR CA PDSCH Demodulation Performance Tests | Qualcomm Incorporated |
| R4-2001446 | Simulation results on NR UE normal CA performance requirements | Huawei, HiSilicon |
| R4-2001447 | Discussion on NR Rel-16 UE CA normal demodulation requirements | Huawei, HiSilicon |
| R4-2001448 | Discussion on HARQ timing for NR UE normal CA performance requirements | Huawei, HiSilicon |
| 8.18.1.2 | PMI reporting requirements with larger number of Tx ports [NR_perf_enh-Perf] | |
| R4-2000138 | Discussion on PMI reporting requirements for larger number of Tx ports | China Telecom |
| R4-2000139 | Initial simulation results for wideband PMI reporting requirements | China Telecom |
| R4-2000300 | Simulation results of PMI test cases | Samsung |
| R4-2000301 | Initial simulation results for PMI reporting with type II codebook | Samsung |
| R4-2000302 | Test case design for PMI reporting with Type II codebook | Samsung |
| R4-2000374 | Simulation results for PMI test cases with 16,32 ports | Intel Corporation |
| R4-2001476 | Ideal and impairment simulation results for PMI reporting test | Huawei, HiSilicon |
| R4-2001477 | Discussion on PMI Type I test of Tx ports larger than 8 | Huawei, HiSilicon |
| R4-2001478 | Discussion on PMI Type II test for Tx ports larger than 8 | Huawei, HiSilicon |
| R4-2001733 | Simulation results for CSI PMI test cases | Ericsson |
| R4-2001734 | Summary of simulation results of NR UE CSI with 16, and 32Tx antennas | Ericsson |
| R4-2002041 | Parameters and simulation results on PMI reporting requirements with larger number of Tx ports | Qualcomm Incorporated |
| 8.18.1.3 | LTE-NR co-existence for TDD [NR_perf_enh-Perf] | |
| R4-2000364 | CR to TS 38.101-4: LTE-NR coexistence requirements for TDD mode (R16) | Intel Corporation |
| R4-2001861 | Simulation results for TDD LTE-NR Coexistence | Qualcomm Incorporated |
| R4-2002427 | CR to TS 38.101-4: LTE-NR coexistence requirements for TDD mode (R16) | Intel Corporation |
| 8.18.1.4 | FR1 CA power imbalance requirements [NR_perf_enh-Perf] | |
| R4-2000140 | FR1 CA PDSCH demodulation requirement with power imbalance | China Telecom |
| R4-2000365 | Discussion on FR1 CA power imbalance requirements | Intel Corporation |
| R4-2000953 | Further discussion on power imbalance requirement for intra-band EN-DC/NR CA | NTT DOCOMO, INC. |
| 8.18.2.1 | 30% TP test point [NR_perf_enh-Perf] | |
| R4-2000141 | PUSCH demodulation requirements for 30% throughput | China Telecom |
| R4-2000299 | Discussion and initial results for NR demodulation performance in Rel-16 | Samsung |
| R4-2000403 | Discussion on PUSCH demodulation requirements at 30% throughput test point | Ericsson |
| R4-2000614 | Discussion on PUSCH performance requirement with 30% throughput metric | CATT |
| R4-2000615 | CR for TS38.104: Introducing PUSCH performance requirements at 30% throughput testing point | CATT |
| R4-2000616 | CR for TS38.141-1: Introducing PUSCH performance requirements at 30% throughput testing point | CATT |
| R4-2000617 | CR for TS38.141-2: Introducing PUSCH performance requirements at 30% throughput testing point | CATT |
| R4-2000811 | Discussion on Rel-16 demodulation requirements for 30% throughput testing points | ZTE Wistron Telecom AB |
| R4-2000812 | Simulation results for NR PUSCH with 30% throughput | ZTE Wistron Telecom AB |
| R4-2001194 | Remaining issues on 30% TP test point for BS demodulation | NTT DOCOMO, INC. |
| R4-2001449 | Discussion on the PUSCH performance requirements at 30% max throughput test point | Huawei, HiSilicon |
| R4-2001692 | NR Rel-16 performance requirement enhancement BS demodulation simulation results and general discussion | Nokia, Nokia Shanghai Bell |
| R4-2002398 | CR for TS38.104: Introducing PUSCH performance requirements at 30% throughput testing point | CATT |
| R4-2002399 | CR for TS38.141-1: Introducing PUSCH performance requirements at 30% throughput testing point | CATT |
| R4-2002400 | CR for TS38.141-2: Introducing PUSCH performance requirements at 30% throughput testing point | CATT |
| 8.18.2.2 | Additional FR2 requirements [NR_perf_enh-Perf] | |
| R4-2000142 | Summary of ideal and impairment results for FR2 PUSCH 2T2R MCS12 | China Telecom |
| R4-2000799 | CR for 38.104: new FRC tables for FR2 PUSCH 2T2R MCS12 | ZTE Wistron Telecom AB |
| R4-2000800 | CR for 38.141-2: new FRC tables for FR2 PUSCH 2T2R MCS12 | ZTE Wistron Telecom AB |
| R4-2001693 | CR for 38.104: Performance requirements for FR2 PUSCH 2T2R 16QAM | Nokia, Nokia Shanghai Bell |
| R4-2001694 | CR for 38.141-2: Radiated test requirements for FR2 PUSCH 2T2R 16QAM | Nokia, Nokia Shanghai Bell |
| R4-2002401 | CR for 38.104: new FRC tables for FR2 PUSCH 2T2R MCS12 | ZTE Wistron Telecom AB |
| R4-2002402 | CR for 38.141-2: new FRC tables for FR2 PUSCH 2T2R MCS12 | ZTE Wistron Telecom AB |
| R4-2002403 | CR for 38.104: Performance requirements for FR2 PUSCH 2T2R 16QAM | Nokia, Nokia Shanghai Bell |
| R4-2002404 | CR for 38.141-2: Radiated test requirements for FR2 PUSCH 2T2R 16QAM | Nokia, Nokia Shanghai Bell |
| 8.19 | Over the air (OTA) base station (BS) testing TR [OTA_BS_testing-Perf] | |
| R4-2001698 | TP to TR 37.9xx : Test uncertainty annexes | Huawei |
| R4-2001699 | OTA BS testing Tx FR1 MU calculation tables | Huawei |
| R4-2001700 | OTA BS testing Tx FR2 MU calculation tables | Huawei |
| R4-2001701 | OTA BS testing RX FR1 MU calculation tables | Huawei |
| R4-2001702 | OTA BS testing FR1 co-location MU calculation tables | Huawei |
| R4-2001703 | TP to TR 37.9xx : Colocation MU value derivation sub-clause updates | Huawei |
| R4-2001704 | TP to TR 37.9xx - OTA BS testing summary clauses 17-18 | Huawei |
| R4-2001705 | TP to TR 37.9xx -Tx MU value derivation sub-clause update | Huawei |
| R4-2001715 | TP to OTA BS TR on EMC | ZTE Corporation |
| R4-2002375 | Email discussion summary for RAN4#94e_#84_OTA_BS_testing | Moderator (Huawei) |
| R4-2002431 | OTA BS testing Tx FR1 MU calculation tables | Huawei |
| R4-2002432 | OTA BS testing Tx FR2 MU calculation tables | Huawei |
| R4-2002433 | OTA BS testing RX FR1 MU calculation tables | Huawei |
| R4-2002442 | TP to TR 37.9xx : Colocation MU value derivation sub-clause updates | Huawei |
| R4-2002443 | TP to OTA BS TR on EMC | ZTE Corporation |
| R4-2002444 | TP to TR 37.9xx : Test uncertainty annexes | Huawei |
| R4-2002513 | Email discussion summary for RAN4#94e_#84_OTA_BS_testingEmail discussion summary for RAN4#94e_#84_OTA_BS_testing | Moderator (Huawei) |
| 8.19.1 | General (such as work plan, AH minutes) [OTA_BS_testing-Perf] | |
| R4-2001806 | Work-plan for the OTA BS testing WI | Huawei |
| R4-2001807 | Skeleton for TR 37.941 on OTA BS testing, Rel-15 | Huawei |
| R4-2001823 | Big TP for TR 37.941, Rel-15 | Huawei |
| 8.19.2 | Others [OTA_BS_testing-Perf] | |
| R4-2001808 | TP to the TR 37.941: Scope | Huawei |
| R4-2001809 | TP to the TR 37.941: general sections | Huawei |
| R4-2001810 | TP to the TR 37.941: Coordinate system | Huawei |
| R4-2001811 | TP to the TR 37.941: conformance testing framework | Huawei |
| R4-2001812 | TP to the TR 37.941: measurement types | Huawei |
| R4-2001813 | TP to the TR 37.941: OTA measurement systems | Huawei |
| R4-2001814 | TP to the TR 37.941: measurement systems calibration | Huawei |
| R4-2001815 | TP to the TR 37.941: TX directional requirements | Huawei |
| R4-2001816 | TP to the TR 37.941: RX directional requirements | Huawei |
| R4-2001817 | TP to the TR 37.941: In-band TRP requirements | Huawei |
| R4-2001818 | TP to the TR 37.941: Out-of-band TRP requirements | Huawei |
| R4-2001819 | TP to the TR 37.941: Out-of-band blocking requirements | Huawei |
| R4-2001820 | TP to the TR 37.941: Demodulation performance requirements | Huawei |
| R4-2001821 | TP to the TR 37.941: EMC requirements | Huawei |
| R4-2001822 | TP to the TR 37.941: annex D, E, F | Huawei |
| R4-2002430 | Big TP for TR 37.941, Rel-15 | Huawei |
| R4-2002434 | TP to the TR 37.941: Scope | Huawei |
| R4-2002435 | TP to the TR 37.941: conformance testing framework | Huawei |
| R4-2002436 | TP to the TR 37.941: measurement types | Huawei |
| R4-2002437 | TP to the TR 37.941: OTA measurement systems | Huawei |
| R4-2002438 | TP to the TR 37.941: TX directional requirements | Huawei |
| R4-2002439 | TP to the TR 37.941: In-band TRP requirements | Huawei |
| R4-2002440 | TP to the TR 37.941: Out-of-band TRP requirements | Huawei |
| R4-2002441 | TP to the TR 37.941: Out-of-band blocking requirements | Huawei |
| 8.20 | 2-step RACH for NR [NR_2step_RACH-Perf] | |
| R4-2000802 | 2-step RACH workplan | ZTE Wistron Telecom AB |
| R4-2002387 | Email discussion summary for RAN4#94e_#96_NR_2step_RACH_Demod | Moderator (ZTE) |
| R4-2002389 | Wayforward on BS demodulation requirements for 2-step RACHW | ZTE |
| R4-2002525 | Email discussion summary for RAN4#94e_#96_NR_2step_RACH_Demod | Moderator (ZTE) |
| R4-2002535 | Email discussion summary for RAN4#94e_#96_NR_2step_RACH_Demod | Moderator (ZTE) |
| 8.20.1 | BS Demodulation requirements (38.104/38.141-1/38.141-2) [NR_2step_RACH-Perf] | |
| R4-2000314 | View on BS demodulation requirement for NR 2-step RACH | Samsung |
| R4-2000801 | BS demodulation requirements for 2-step RACH | ZTE Wistron Telecom AB |
| R4-2001183 | On 2 step RACH demodulation | Ericsson |
| R4-2001491 | On 2-step RACH BS demodulation requirements | Nokia, Nokia Shanghai Bell |
| 8.20.2 | Others [NR_2step_RACH-Perf] | |
| R4-2001279 | Discussion on RRM requirements for 2-step RACH | ZTE |
| R4-2001492 | On RRM core requirements for 2-step RACH | Nokia, Nokia Shanghai Bell |
| R4-2002129 | Impact of Two Step RACH WI in RRM requirements | Qualcomm |
| R4-2002191 | Email discussion summary for RAN4#94e_#68_NR_2step_RACH_RRM | Moderator (ZTE) |
| R4-2002259 | WF on 2-step RACH RRM requirements | ZTE |
| R4-2002322 | Email discussion summary for RAN4#94e_#68_NR_2step_RACH_RRM | Moderator (ZTE) |
| 8.21.1 | MDT related RRM requirements (38.133, 36.133) [NR_SON_MDT-Core] | |
| R4-2000648 | Discussion on RRM requirements for Rel-16 MDT | CMCC |
| R4-2000649 | CR on logged MDT requirements (2, 3.3, 4.3, 5.3) | CMCC, Ericsson |
| R4-2000650 | CR on logged MDT requirements (2, 4.3) | CMCC, Ericsson |
| R4-2001671 | Discussion on SON/MDT support for NR on RRM impact | Huawei, HiSilicon |
| R4-2001951 | On UE requirements for NR MDT | Ericsson, CMCC |
| R4-2001952 | Response LS on MDT Measurements | Ericsson |
| R4-2002192 | Email discussion summary for RAN4#94e_#69_NR_SON_MDT_RRM | Moderator (CMCC) |
| R4-2002260 | WF on MDT RRM requirements | CMCC |
| R4-2002261 | Response LS on MDT Measurements | Ericsson |
| R4-2002262 | CR on logged MDT requirements (2, 3.3, 4.3, 5.3) | CMCC, Ericsson |
| R4-2002263 | CR on logged MDT requirements (2, 4.3) | CMCC, Ericsson |
| R4-2002323 | Email discussion summary for RAN4#94e_#69_NR_SON_MDT_RRM | Moderator (CMCC) |
| R4-2002344 | CR on logged MDT requirements (2, 4.3) | CMCC, Ericsson |
| 9.1 | NR intra band Carrier Aggregation for xCC DL/yCC UL including contiguous and non-contiguous spectrum (x>=y) [NR_CA_R16_intra] | |
| R4-2002698 | Email discussion summary for RAN4#94e_#25_NR_Baskets_Part_1 | Moderator (Nokia) |
| 9.1.1 | Rapporteur Input (WID/TR/CR) [NR_CA_R16_intra-Core /Perf] | |
| R4-2001499 | Revised WID NR Intra-band Rel-16 | Ericsson |
| R4-2001502 | TR 38.716-01-01 v0.9.0 Rel-16 NR Intra-band | Ericsson |
| R4-2001506 | TP for TR 38.716-01-01 for updated scope from RAN #86 | Ericsson |
| R4-2001510 | CR introduction completed band combinations 38.716-01-01 -> 38.101-1 | Ericsson |
| R4-2001511 | CR introduction completed band combinations 38.716-01-01 -> 38.101-2 | Ericsson |
| R4-2001515 | Rel-16 CR to 38.101-1 for editorial corrections | Ericsson |
| R4-2001516 | Rel-16 CR to 38.101-2 for editorial corrections | Ericsson |
| R4-2002025 | Rel-16 CR to 38.101-2 for editorial corrections | Ericsson |
| R4-2002575 | Rel-16 CR to 38.101-1 for editorial corrections | Ericsson |
| R4-2002611 | Revised WID NR Intra-band Rel-16 | Ericsson |
| 9.1.2 | UE RF for FR1 [NR_CA_R16_intra-Core] | |
| R4-2000127 | Editorial correction of NR CA bandwidth classe | Verizon, Ericsson |
| R4-2000328 | CR to TS 38.101-1 on corrections to intra-band non-contiguous CA operating bands (Rel-16) | ZTE Corporation |
| R4-2000418 | CR for 38.101-1: Corrections to intra-band CA tables | Sprint Corporation |
| R4-2000520 | CA_n48B A-MPR | Nokia |
| R4-2000563 | CR to TS 38.101-1 on corrections to NR CA bandwidth classes (Rel-16) | ZTE Corporation |
| R4-2000794 | TP for TR 38.716-01-01: CA_3DL_n77(3A)_1UL_n77A | SoftBank Corp. |
| R4-2002581 | CR to TS 38.101-1 on corrections to intra-band non-contiguous CA operating bands (Rel-16) | ZTE Corporation |
| R4-2002582 | CR for 38.101-1: Corrections to intra-band CA tables | Sprint Corporation |
| R4-2002600 | TP for TR 38.716-01-01: CA_3DL_n77(3A)_1UL_n77A | SoftBank Corp. |
| R4-2002911 | CR for 38.101-1: Corrections to intra-band CA tables | Sprint Corporation |
| 9.2 | NR inter-band Carrier Aggregation/Dual Connectivity for 2 bands DL with x bands UL (x=1, 2) [NR_CADC_R16_2BDL_xBUL] | |
| R4-2002699 | Email discussion summary for RAN4#94e_#26_NR_Baskets_Part_2 | Moderator (Nokia) |
| 9.2.1 | Rapporteur Input (WID/TR/CR) [NR_CADC_R16_2BDL_xBUL-Core/Perf] | |
| R4-2000497 | CR to reflect the completed NR inter band CA DC combinations for 2 bands DL with up to 2 bands UL into Rel16 TS 38.101-1 | ZTE Corporation |
| R4-2000498 | CR to reflect the completed NR inter band CA DC combinations for 2 bands DL with up to 2 bands UL into Rel16 TS 38.101-3 | ZTE Corporation |
| R4-2000502 | Revised WID on Rel-16 NR Inter-band Carrier Aggregation/Dual Connectivity for 2 bands DL with x bands UL (x=1,2) | ZTE Corporation |
| R4-2000803 | TR 38.716-02-00 v090 | ZTE Wistron Telecom AB |
| 9.2.2 | NR inter band CA without any FR2 band(s) [NR_CADC_R16_2BDL_xBUL-Core] | |
| R4-2000128 | Editorial correction of band n66 bandwidth | Verizon, Ericsson |
| R4-2000143 | TP for TR38.716-02-00: Requirements for DL CA_n29A-n70A, DL CA_n29A-n66B, DL CA_n29A-n66(2A) and for UL CA_n66A-n71A, UL CA_n70A-n71A | Dish Network |
| R4-2000181 | TP to TR 38.716-02-00: CA_n28-n78 | Nokia, Nokia Shanghai Bell, BT plc |
| R4-2000183 | TP to TR 38.716-02-00: CA_n41-n66 | Nokia, Nokia Shanghai Bell, T-Mobile USA |
| R4-2000184 | TP to TR 38.716-02-00: CA_n41-n71 | Nokia, Nokia Shanghai Bell, T-Mobile USA |
| R4-2000189 | TP to TR 38.716-02-00: Corrections to CA_n5-n261 and CA_n66-n261 | Nokia, Nokia Shanghai Bell |
| R4-2000448 | CR to TS 38.101-1: Corrections on MSD tables for CA_n20-n78 and CA_n66-n78 | Xiaomi |
| R4-2000478 | TP for TR 38.716-02-00: CA_n3A-n38A | ZTE Corporation |
| R4-2000691 | TP for TR 38.716-02-00 CA_n2A_n66A | Verizon UK Ltd |
| R4-2000692 | TP for TR 38.716-02-00 CA_n5A_n66A | Verizon UK Ltd |
| R4-2000831 | TP for TR 38.716-02-00: CA_n2-n78 | Huawei, HiSilicon |
| R4-2000832 | TP for TR 38.716-02-00: CA_n38-n66 | Huawei, HiSilicon |
| R4-2000833 | TP for TR 38.716-02-00: CA_n7-n25 | Huawei, HiSilicon |
| R4-2000834 | TP for TR 38.716-02-00: CA_n25-n66 | Huawei, HiSilicon |
| R4-2000835 | TP for TR 38.716-02-00: CA_n25-n78 | Huawei, HiSilicon |
| R4-2000836 | TP for TR 38.716-02-00: CA_n66A-n78(2A) | Huawei, HiSilicon |
| R4-2001060 | Updated TP for TR 38.716-02-00: CA_n1A-n78(2A) | Huawei, HiSilicon, BT plc |
| R4-2001061 | TP for TR 38.716-02-00: CA_n20-n75 | Huawei, HiSilicon |
| R4-2001062 | Draft CR for 38.101-1 to correct editoral errors | Huawei, HiSilicon |
| R4-2001071 | Discussion on improvement of Reference sensitivity exception table in 38.101-1 and 38.101-3 | Huawei, HiSilicon |
| R4-2001072 | CR for 38.101-1: improvement of Reference sensitivity exception table (Rel-16) | Huawei, HiSilicon |
| R4-2001073 | CR for 38.101-3: improvement of Reference sensitivity exception table (Rel-16) | Huawei, HiSilicon |
| R4-2001076 | Discussion on introduction of some sub-clause title for NR inter-band CA | Huawei, HiSilicon |
| R4-2001519 | TP for TR 38.716-02-00 to include CA_n20-n78 | Ericsson, Telia, BT plc |
| R4-2002635 | TP for TR38.716-02-00: Requirements for DL CA_n29A-n70A, DL CA_n29A-n66B, DL CA_n29A-n66(2A) and for UL CA_n66A-n71A, UL CA_n70A-n71A | Dish Network |
| R4-2002636 | TP to TR 38.716-02-00: CA_n28-n78 | Nokia, Nokia Shanghai Bell, BT plc |
| R4-2002637 | TP to TR 38.716-02-00: CA_n41-n66 | Nokia, Nokia Shanghai Bell, T-Mobile USA |
| R4-2002638 | TP to TR 38.716-02-00: CA_n41-n71 | Nokia, Nokia Shanghai Bell, T-Mobile USA |
| R4-2002639 | TP to TR 38.716-02-00: Corrections to CA_n5-n261 and CA_n66-n261 | Nokia, Nokia Shanghai Bell |
| R4-2002640 | TP for TR 38.716-02-00: CA_n3A-n38A | ZTE Corporation |
| R4-2002641 | TP for TR 38.716-02-00 CA_n2A_n66A | Verizon UK Ltd |
| R4-2002642 | TP for TR 38.716-02-00 CA_n5A_n66A | Verizon UK Ltd |
| R4-2002643 | TP for TR 38.716-02-00: CA_n2-n78 | Huawei, HiSilicon |
| R4-2002644 | TP for TR 38.716-02-00: CA_n38-n66 | Huawei, HiSilicon |
| R4-2002645 | TP for TR 38.716-02-00: CA_n25-n78 | Huawei, HiSilicon |
| R4-2002646 | TP for TR 38.716-02-00: CA_n66A-n78(2A) | Huawei, HiSilicon |
| R4-2002647 | Updated TP for TR 38.716-02-00: CA_n1A-n78(2A) | Huawei, HiSilicon, BT plc |
| R4-2002648 | TP for TR 38.716-02-00: CA_n20-n75 | Huawei, HiSilicon |
| R4-2002714 | TP for TR 38.716-02-00: CA_n25-n66 | Huawei, HiSilicon |
| 9.2.3 | NR inter band CA with at least one FR2 band [NR_CADC_R16_2BDL_xBUL-Core] | |
| R4-2000986 | CR to TS 38.101-3: adding 90MHz channel BW support for Rel.16 CA_n78A-n257 configurations | CHTTL |
| 9.3.1 | Rapporteur Input (WID/TR/CR) [DC_R16_1BLTE_1BNR_2DL2UL-Core/Perf] | |
| R4-2000881 | Updated TR 37.716-11-11 V1.0.0 Rel.16 1 LTE band + 1 NR band EN-DC | CHTTL |
| R4-2000886 | Revised WID for EN-DC of 1 band LTE + 1 band NR | CHTTL |
| R4-2000887 | CR on introduction of completed EN-DC of 1 band LTE and 1 band NR | CHTTL |
| R4-2001517 | Rel-16 CR to 38.101-3 for editorial corrections | Ericsson |
| R4-2002613 | Rel-16 CR to 38.101-3 for editorial corrections | Ericsson |
| 9.3.2 | EN-DC without FR2 band [DC_R16_1BLTE_1BNR_2DL2UL-Core] | |
| R4-2000096 | TP for TR 38.716-11-11 for DC_2A_n48B | Verizon UK Ltd |
| R4-2000097 | TP for TR 37.716-11-11: DC_66_n48 | Verizon UK Ltd |
| R4-2000098 | TP for TR 37.716-11-11: DC_13A_n48B | Verizon UK Ltd |
| R4-2000099 | TP for TR 37.716-11-11: DC_5A_n48B | Verizon UK Ltd |
| R4-2000100 | TP for TR 37.716-11-11: DC_5_n2 | Verizon UK Ltd |
| R4-2000101 | TP for TR 37.716-11-11: DC_5_n66A | Verizon UK Ltd |
| R4-2000474 | TP for TR37.716-11-11:DC_13_n78 | ZTE Corporation, Bell, Telus |
| R4-2000488 | CR to TS 38.101-3: Updated the MSD values for ENDC 3-n41 | ZTE Corporation |
| R4-2000540 | TP for TR 37.716-11-11: DC_66_n12 | Nokia, US Cellular |
| R4-2000541 | TP for TR 37.716-11-11: DC_48_n71 | Nokia, US Cellular |
| R4-2000707 | CR for 38.101-3: Correction of MOP tolerance for DC_39_n41 | Sprint Corporation |
| R4-2000764 | Draft CR for TS 38.101-3: Support of n77(2A) in DC_8_n77, 11_n77 and 28_n77 | SoftBank Corp. |
| R4-2000774 | TP for TR 37.716-11-11: DC_11_n3 | SoftBank Corp. |
| R4-2000775 | TP for TR 37.716-11-11: DC_11_n28 | SoftBank Corp. |
| R4-2000837 | TP for TR 37.716-11-11: DC_13_n7 | Huawei, HiSilicon |
| R4-2000838 | TP for TR 37.716-11-11: DC_13_n78 | Huawei, HiSilicon |
| R4-2000839 | TP for TR 37.716-11-11: DC_66_n38 | Huawei, HiSilicon |
| R4-2000853 | TP to TR 37.716-11-11 DC_20A_n41A | Huawei, HiSilicon |
| R4-2000855 | TP for TR 37.716-11-11: DC_71A_n48A | Comcast |
| R4-2001046 | TP to TR 37.716-11-11: DC_28_n5 | Nokia, Nokia Shanghai Bell |
| R4-2001047 | TP for TR 37.716-11-11: DC_3A_n8A | Huawei, HiSilicon |
| R4-2001048 | TP for TR 37.716-11-11: DC_7A_n8A | Huawei, HiSilicon |
| R4-2001078 | draft CR for 38.101-3 to correct editoral errors for spurious emissions for UE co-existence | Huawei, HiSilicon |
| R4-2001287 | TP for 37.716-11-11 to introduce DC_48_n5 | Nokia, Verizon |
| R4-2001288 | TP for 37.716-11-11 to introduce DC_48_n66 | Nokia, Verizon |
| R4-2001298 | TP for 37.716-11-11 to introduce DC_12_n25 | Nokia, T-Mobile US |
| R4-2001524 | TP for TR 37 716-11-11 to include DC_12A_n78A | Ericsson, Rogers |
| R4-2001525 | TP for TR 37 716-11-11 to include DC_12A_n38A | Ericsson, Rogers |
| R4-2001526 | TP for TR 37 716-11-11 to include DC_5A_n38A | Ericsson, Rogers |
| R4-2001527 | TP for TR 37 716-11-11 to include DC_12A_n7A | Ericsson, Rogers |
| R4-2001528 | TP for TR 37 716-11-11 to include DC_66A_n7A | Ericsson, Rogers |
| R4-2001529 | TP for TR 37 716-11-11 to include DC_71A_n38A | Ericsson, Rogers |
| R4-2001530 | TP for TR 37 716-11-11 to include DC_71A_n66A | Ericsson, Rogers |
| R4-2001531 | TP for TR 37 716-11-11 to include DC_71A_n78A | Ericsson, Rogers |
| R4-2001969 | TP for TR 37 716-11-11 to include DC_2A_n12A | Ericsson, US Cellular |
| R4-2001970 | TP for TR 37 716-11-11 to include DC_5A_n12A | Ericsson, US Cellular |
| R4-2001971 | TP for TR 37 716-11-11 to include DC_48A_n5A | Ericsson, US Cellular |
| R4-2001972 | TP for TR 37 716-11-11 to include DC_48A_n12A | Ericsson, US Cellular |
| R4-2001973 | TP for TR 37 716-11-11 to include DC_12_n71 | Ericsson, US Cellular |
| R4-2002003 | draft Rel-16 CR to 38.101-3 to add missing CA_n7B UL for two band DC combinations | Ericsson, Telstra |
| R4-2002009 | draft Rel-16 CR to 38.101-3 to add new configurations for 2_n41, 66_n41 to existing combinations | Ericsson, T-Mobile US |
| R4-2002049 | TP for TR 37.716-11-11: DC_(n)48 and DC_48_n48 | Google Inc. |
| R4-2002109 | TP for TR 37.716-11-11:DC_48B_n71A | Comcast |
| R4-2002111 | TP for TR 37.716-11-11: DC_48C_n71A | Comcast |
| R4-2002112 | TP for TR 37.716-11-11: DC_48D_n71A | Comcast |
| R4-2002570 | TP for TR 38.716-11-11 for DC_2A_n48B | Verizon UK Ltd |
| R4-2002571 | TP for TR 37.716-11-11: DC_66_n48 | Verizon UK Ltd |
| R4-2002572 | TP for TR 37.716-11-11: DC_5_n2 | Verizon UK Ltd |
| R4-2002573 | TP for TR 37.716-11-11: DC_5_n66A | Verizon UK Ltd |
| R4-2002583 | TP for TR37.716-11-11:DC_13_n78 | ZTE Corporation, Bell, Telus |
| R4-2002584 | CR to TS 38.101-3: Updated the MSD values for ENDC 3-n41 | ZTE Corporation |
| R4-2002597 | TP for TR 37.716-11-11: DC_71A_n48A | Comcast |
| R4-2002598 | TP for TR 37.716-11-11: DC_11_n3 | SoftBank Corp. |
| R4-2002599 | TP for TR 37.716-11-11: DC_11_n28 | SoftBank Corp. |
| R4-2002601 | TP for TR 37.716-11-11: DC_13_n7 | Huawei, HiSilicon |
| R4-2002602 | TP for TR 37.716-11-11: DC_66_n38 | Huawei, HiSilicon |
| R4-2002603 | TP to TR 37.716-11-11 DC_20A_n41A | Huawei, HiSilicon |
| R4-2002604 | TP to TR 37.716-11-11: DC_28_n5 | Nokia, Nokia Shanghai Bell |
| R4-2002605 | TP for TR 37.716-11-11: DC_3A_n8A | Huawei, HiSilicon |
| R4-2002606 | TP for TR 37.716-11-11: DC_7A_n8A | Huawei, HiSilicon |
| R4-2002607 | draft CR for 38.101-3 to correct editoral errors for spurious emissions for UE co-existence | Huawei, HiSilicon |
| R4-2002609 | TP for 37.716-11-11 to introduce DC_48_n66 | Nokia, Verizon |
| R4-2002614 | TP for TR 37 716-11-11 to include DC_5A_n38A | Ericsson, Rogers |
| R4-2002615 | TP for TR 37 716-11-11 to include DC_71A_n66A | Ericsson, Rogers |
| R4-2002616 | TP for TR 37 716-11-11 to include DC_71A_n78A | Ericsson, Rogers |
| R4-2002617 | TP for TR 37 716-11-11 to include DC_48A_n5A | Ericsson, US Cellular |
| R4-2002618 | TP for TR 37 716-11-11 to include DC_48A_n12A | Ericsson, US Cellular |
| R4-2002619 | TP for TR 37 716-11-11 to include DC_12_n71 | Ericsson, US Cellular |
| R4-2002630 | TP for TR 37.716-11-11:DC_48B_n71A | Comcast |
| R4-2002631 | TP for TR 37.716-11-11: DC_48C_n71A | Comcast |
| R4-2002632 | TP for TR 37.716-11-11: DC_48D_n71A | Comcast |
| 9.3.3 | EN-DC with FR2 band [DC_R16_1BLTE_1BNR_2DL2UL-Core] | |
| R4-2000126 | Introduction of completed EN-DC of 1 band LTE and 1 band NR | Verizon, Ericsson |
| R4-2002574 | Introduction of completed EN-DC of 1 band LTE and 1 band NR | Verizon, Ericsson |
| 9.4.1 | Rapporteur Input (WID/TR/CR) [DC_R16_2BLTE_1BNR_3DL2UL-Core/Perf] | |
| R4-2000840 | TR 37.716-21-11 v0.9.0 | Huawei, HiSilicon |
| R4-2000841 | Revised WID: Dual Connectivity (EN-DC) of 2 bands LTE inter-band CA (2DL/1UL) and 1 NR band (1DL/1UL) | Huawei, HiSilicon |
| R4-2000842 | CR on introduction of completed EN-DC of 2 bands LTE and 1 band NR from RAN4#94-e into TS 38.101-3 | Huawei, HiSilicon |
| 9.4.2 | EN-DC without FR2 band [DC_R16_2BLTE_1BNR_3DL2UL-Core] | |
| R4-2000237 | TP for TR 37.716-21-11: DC_2-2-13_n66 | Samsung, Verizon |
| R4-2000238 | TP for TR 37.716-21-11: DC_2-5_n2 and DC_2-5-5_n2 | Samsung, Verizon |
| R4-2000239 | TP for TR 37.716-21-11: DC_2-5_n5 and DC_2-2-5_n5 | Samsung, Verizon |
| R4-2000240 | TP for TR 37.716-21-11: DC_2-5_n66 and DC_2-5-5_n66 | Samsung, Verizon |
| R4-2000241 | TP for TR 37.716-21-11: DC_2-13_n2 | Samsung, Verizon |
| R4-2000242 | TP for TR 37.716-21-11: DC_2-13_n5 and DC_2-2-13_n5 | Samsung, Verizon |
| R4-2000243 | TP for TR 37.716-21-11: DC_2-66_n48 and DC_2-66-66_n48 | Samsung, Verizon |
| R4-2000244 | TP for TR 37.716-21-11: DC_5-5-66_n66 and DC_5-5-66-66_n66 | Samsung, Verizon |
| R4-2000245 | TP for TR 37.716-21-11: DC_5-13_n2 | Samsung, Verizon |
| R4-2000246 | TP for TR 37.716-21-11: DC_5-66_n2, DC_5-5-66_n2, DC_5-66-66_n2 and DC_5-5-66-66_n2 | Samsung, Verizon |
| R4-2000247 | TP for TR 37.716-21-11: DC_5-66_n66 and DC_5-66-66_n66 | Samsung, Verizon |
| R4-2000248 | TP for TR 37.716-21-11: DC_5-66-66_n5 | Samsung, Verizon |
| R4-2000249 | TP for TR 37.716-21-11: DC_13-46_n5 | Samsung, Verizon |
| R4-2000250 | TP for TR 37.716-21-11: DC_13-66_n2 and DC_13-66-66_n2 | Samsung, Verizon |
| R4-2000251 | TP for TR 37.716-21-11: DC_13-66_n48 and DC_13-66-66_n48 | Samsung, Verizon |
| R4-2000252 | TP for TR 37.716-21-11: DC_13A-66A-66A_n66A | Samsung, Verizon |
| R4-2000416 | TP for TR 37.716-21-11: DC_25A-41D_n41A correction | Sprint Corporation |
| R4-2000417 | CR for 38.101-3: DC_25-41_n41 correction | Sprint Corporation |
| R4-2000479 | TP for TR37.716-21-11: DC_5A-66A_n78 | ZTE Corporation, Bell, Telus |
| R4-2000528 | TP to TR 37.716-21-11: DC_(n)12AA | Nokia, US Cellular |
| R4-2000529 | TP to TR 37.716-21-11: DC_(n)5AA | Nokia, US Cellular |
| R4-2000530 | TP to TR 37.716-21-11: DC_2A-12A_n71A | Nokia, US Cellular |
| R4-2000531 | TP to TR 37.716-21-11: DC_5A-12A_n71A | Nokia, US Cellular |
| R4-2000532 | TP to TR 37.716-21-11: DC_2A-5A_n71A | Nokia, US Cellular |
| R4-2000533 | TP to TR 37.716-21-11: DC_2A-48A_n71A | Nokia, US Cellular |
| R4-2000534 | TP to TR 37.716-21-11: DC_5A-48A_n71A | Nokia, US Cellular |
| R4-2000535 | TP to TR 37.716-21-11: DC_48A_(n)12AA | Nokia, US Cellular |
| R4-2000536 | TP to TR 37.716-21-11: DC_66A_(n)12AA | Nokia, US Cellular |
| R4-2000740 | Draft CR to TS 38.101-3: Adding DC_1A-7C_n3A | VODAFONE Group Plc |
| R4-2000741 | Draft CR to TS 38.101-3: Adding DC_7C-20A_n3A | VODAFONE Group Plc |
| R4-2000742 | Draft CR to TS 38.101-3: Adding DC_7C-20A_n1A | VODAFONE Group Plc |
| R4-2000766 | Draft CR for TS 38.101-3: Support of n77(2A) in DC_1-8_n77, 1-11_n77, 3-28_n77 and 8-11_n77 | SoftBank Corp. |
| R4-2000843 | TP for TR 37.716-21-11: DC_2-66_n38 | Huawei, HiSilicon |
| R4-2000844 | TP for TR 37.716-21-11: DC_3C-8A_n1A | Huawei, HiSilicon |
| R4-2000874 | TP for TR 37.716-21-11: DC_1A-18A_n3A | KDDI Corporation |
| R4-2000876 | TP for TR 37.716-21-11 DC_1A-28A_n3A | KDDI Corporation |
| R4-2001045 | TP to TR 37.716-21-11: CA_3-20_n7 | Nokia, Nokia, Shanghai Bell, BT plc |
| R4-2001049 | TP for TR 37.716-21-11: DC_1A-3A_n8A | Huawei, HiSilicon |
| R4-2001050 | TP for TR 37.716-21-11: DC_1A-7A_n8A | Huawei, HiSilicon |
| R4-2001051 | TP for TR 37.716-21-11: DC_1A-20A_n8A | Huawei, HiSilicon |
| R4-2001052 | TP for TR 37.716-21-11: DC_3A-7A_n8A | Huawei, HiSilicon |
| R4-2001053 | TP for TR 37.716-21-11: DC_3A-20A_n8A | Huawei, HiSilicon |
| R4-2001054 | TP for TR 37.716-21-11: DC_7A-20A_n8A | Huawei, HiSilicon |
| R4-2001055 | updated TP for TR 37.716-21-11: add UL DC_1_n38 for DC_1-20_n38 | Huawei, HiSilicon |
| R4-2001056 | TP for TR 37.716-21-11: DC_1A-41A_n41A\DC_1A-41C_n41A | Huawei, HiSilicon |
| R4-2001057 | TP for TR 37.716-21-11: DC_1A-(n)41AA\DC_1A-(n)41CA | Huawei, HiSilicon |
| R4-2001058 | Updated TP for TR 37.716-21-11: DC_7C-20A_n1A | Huawei, HiSilicon, BT plc |
| R4-2001059 | Draft CR for TS 38.101-3: adding UL configurations for DC_3A-7C_n78A/DC_3C-7C_n78A | Huawei, HiSilicon, BT plc |
| R4-2001299 | TP for 37.716-21-11 to introduce DC_2-66_n25 | Nokia, T-Mobile US |
| R4-2001300 | TP for 37.716-21-11 to introduce DC_12-66_n25 | Nokia, T-Mobile US |
| R4-2001301 | TP for 37.716-21-11 to introduce DC_46-66_n25 | Nokia, T-Mobile US |
| R4-2001532 | TP for TR 37.716-21-11 to include DC_2-7_n38 | Ericsson, Rogers |
| R4-2001533 | TP for TR 37.716-21-11 to include DC_2-71_n38 | Ericsson, Rogers |
| R4-2001534 | TP for TR 37.716-21-11 to include DC_7-66_n38 | Ericsson, Rogers |
| R4-2001535 | TP for TR 37.716-21-11 to include DC_66-71_n38 | Ericsson, Rogers |
| R4-2001536 | TP for TR 37.716-21-11 to include DC_2-66_n38 | Ericsson, Rogers |
| R4-2001537 | TP for TR 37.716-21-11 to include DC_7-66_n71 | Ericsson, Samsung, Rogers |
| R4-2001538 | TP for TR 37.716-21-11 to include DC_2-71_n66 | Ericsson, Rogers |
| R4-2001539 | TP for TR 37.716-21-11 to include DC_66-71_n66 | Ericsson, Rogers |
| R4-2001540 | TP for TR 37.716-21-11 to include DC_2-71_n78 | Ericsson, Rogers |
| R4-2001541 | TP for TR 37.716-21-11 to include DC_66-71_n78 | Ericsson, Rogers |
| R4-2001974 | TP for TR 37 716-21-11 to include DC_2A-48A_n12A | Ericsson, US Cellular |
| R4-2001975 | TP for TR 37 716-21-11 to include DC_2A-66A_n12A | Ericsson, US Cellular |
| R4-2001976 | TP for TR 37 716-21-11 to include DC_5A-66A_n71A | Ericsson, US Cellular, MediaTek |
| R4-2001977 | TP for TR 37 716-21-11 to include DC_12A-48A_n71A | Ericsson, US Cellular |
| R4-2001978 | TP for TR 37 716-21-11 to include DC_12A-66A_n71A | Ericsson, US Cellular |
| R4-2001979 | TP for TR 37 716-21-11 to include DC_48A-66A_n12A | Ericsson, US Cellular |
| R4-2001980 | TP for TR 37 716-21-11 to include DC_48A-66A_n71A | Ericsson, US Cellular, MediaTek |
| R4-2002004 | draft Rel-16 CR to 38.101-3 to add CA_n7B UL for three band DC combinations | Ericsson, Telstra |
| R4-2002007 | TP for TR 37.716-21-11 to include DC_7A-28A_n3A, DC_7C-28A_n3A | Ericsson, Telstra |
| R4-2002010 | draft Rel-16 CR to 38.101-3 to add new configurations for 2-66_n41 to existing combinations | Ericsson, T-Mobile US |
| R4-2002012 | TP for TR 37 716-21-11 to include DC_2-46_n66 | Ericsson, T-Mobile US, MediaTek |
| R4-2002576 | TP for TR 37.716-21-11: DC_2-66_n48 and DC_2-66-66_n48 | Samsung, Verizon |
| R4-2002577 | TP for TR 37.716-21-11: DC_5-66_n2, DC_5-5-66_n2, DC_5-66-66_n2 and DC_5-5-66-66_n2 | Samsung, Verizon |
| R4-2002578 | TP for TR 37.716-21-11: DC_13-46_n5 | Samsung, Verizon |
| R4-2002579 | TP for TR 37.716-21-11: DC_13-66_n2 and DC_13-66-66_n2 | Samsung, Verizon |
| R4-2002580 | TP for TR 37.716-21-11: DC_13-66_n48 and DC_13-66-66_n48 | Samsung, Verizon |
| R4-2002585 | TP to TR 37.716-21-11: DC_(n)12AA | Nokia, US Cellular |
| R4-2002586 | TP to TR 37.716-21-11: DC_(n)5AA | Nokia, US Cellular |
| R4-2002587 | TP to TR 37.716-21-11: DC_2A-12A_n71A | Nokia, US Cellular |
| R4-2002588 | TP to TR 37.716-21-11: DC_5A-12A_n71A | Nokia, US Cellular |
| R4-2002610 | TP for 37.716-21-11 to introduce DC_46-66_n25 | Nokia, T-Mobile US |
| R4-2002620 | TP for TR 37 716-21-11 to include DC_12A-48A_n71A | Ericsson, US Cellular |
| R4-2002621 | TP for TR 37 716-21-11 to include DC_12A-66A_n71A | Ericsson, US Cellular |
| R4-2002628 | draft Rel-16 CR to 38.101-3 to add CA_n7B UL for three band DC combinations | Ericsson, Telstra |
| 9.4.3 | EN-DC with FR2 band [DC_R16_2BLTE_1BNR_3DL2UL-Core] | |
| R4-2000253 | TP for TR 37.716-21-11: DC_2-5_n260 | Samsung, Verizon |
| R4-2000254 | TP for TR 37.716-21-11: DC_2-5_n261 | Samsung, Verizon |
| R4-2000255 | TP for TR 37.716-21-11: DC_2-13_n260 | Samsung, Verizon |
| R4-2000256 | TP for TR 37.716-21-11: DC_2-13_n261 | Samsung, Verizon |
| R4-2000257 | TP for TR 37.716-21-11: DC_2-66_n260 and DC_2-66-66_n260 | Samsung, Verizon |
| R4-2000258 | TP for TR 37.716-21-11: DC_2-66_n261 and DC_2-66-66_n261 | Samsung, Verizon |
| R4-2000259 | TP for TR 37.716-21-11: DC_5-66_n260 and DC_5-66-66_n260 | Samsung, Verizon |
| R4-2000260 | TP for TR 37.716-21-11: DC_5-66_n261 and DC_5-66-66_n261 | Samsung, Verizon |
| R4-2000261 | TP for TR 37.716-21-11: DC_13-66_n260 and DC_13-66-66_n260 | Samsung, Verizon |
| R4-2000262 | TP for TR 37.716-21-11: DC_13-66_n261 and DC_13-66-66_n261 | Samsung, Verizon |
| 9.5.1 | Rapporteur Input (WID/TR/CR) [DC_R16_3BLTE_1BNR_4DL2UL-Core/Perf] | |
| R4-2001500 | Revised WID LTE 3DL and one NR band Rel-16 | Ericsson |
| R4-2001503 | TR 37.716-31-11 v0.9.0 Rel-16 DC combinations LTE 3DL and one NR band | Ericsson |
| R4-2001507 | TP for TR 37.716-31-11 for updated scope from RAN #86 | Ericsson |
| R4-2001512 | CR introduction completed band combinations 37.716-31-11 -> 38.101-3 | Ericsson |
| R4-2002612 | Revised WID LTE 3DL and one NR band Rel-16 | Ericsson |
| 9.5.2 | EN-DC without FR2 band [DC_R16_3BLTE_1BNR_4DL2UL-Core] | |
| R4-2000542 | TP to TR 37.716-31-11: Addition of DC_2A-5A_(n)12AA | Nokia, US Cellular |
| R4-2000543 | TP to TR 37.716-31-11: Addition of DC_2A-5A-48A_n12A | Nokia, US Cellular |
| R4-2000544 | TP to TR 37.716-31-11: Addition of DC_ 2A-5A-66A_n12A | Nokia, US Cellular |
| R4-2000545 | TP to TR 37.716-31-11: Addition of DC_2A-12A_(n)5AA | Nokia, US Cellular |
| R4-2000546 | TP to TR 37.716-31-11: Addition of DC_2A-12A-48A_n5A | Nokia, US Cellular |
| R4-2000547 | TP to TR 37.716-31-11: Addition of DC_2A-12A-66A_n5A | Nokia, US Cellular |
| R4-2000548 | TP to TR 37.716-31-11: Addition of DC_2A-48A_(n)5AA | Nokia, US Cellular |
| R4-2000549 | TP to TR 37.716-31-11: Addition of DC_2A-48A-66A_n5A | Nokia, US Cellular |
| R4-2000550 | TP to TR 37.716-31-11: Addition of DC_2A-66A_(n)5AA | Nokia, US Cellular |
| R4-2000551 | TP to TR 37.716-31-11: Addition of DC_5A-48A_(n)12AA | Nokia, US Cellular |
| R4-2000552 | TP to TR 37.716-31-11: Addition of DC_5A-48A-66A_n12A | Nokia, US Cellular |
| R4-2000553 | TP to TR 37.716-31-11: Addition of DC_5A-66A_(n)12AA | Nokia, US Cellular |
| R4-2000554 | TP to TR 37.716-31-11: Addition of DC_12A-48A_(n)5AA | Nokia, US Cellular |
| R4-2000555 | TP to TR 37.716-31-11: Addition of DC_12A-48A-66A_n5A | Nokia, US Cellular |
| R4-2000556 | TP to TR 37.716-31-11: Addition of DC_12A-66A_(n)5AA | Nokia, US Cellular |
| R4-2000710 | Draft CR to TS 38.101-3: Adding DC_1A-7C-20A_n3A | VODAFONE Group Plc |
| R4-2000739 | Draft CR to TS 38.101-3: Adding DC_3A-7C-20A_n1A | VODAFONE Group Plc |
| R4-2000763 | Draft CR for TS 38.101-3: Support of n77(2A) in DC_1-8-11_n77 | SoftBank Corp. |
| R4-2000845 | TP for TR 37.716-31-11: DC_3C-7A-8A_n1A | Huawei, HiSilicon |
| R4-2001289 | TP for 37.716-31-11 to introduce DC_2-5-66_n2 | Nokia, Verizon |
| R4-2001290 | TP for 37.716-31-11 to introduce DC_2-5-66_n5 | Nokia, Verizon |
| R4-2001291 | TP for 37.716-31-11 to introduce DC_2-5-66_n66 | Nokia, Verizon |
| R4-2001292 | TP for 37.716-31-11 to introduce DC_2-13-66_n2 | Nokia, Verizon |
| R4-2001293 | TP for 37.716-31-11 to introduce DC_2-13-66_n5 | Nokia, Verizon |
| R4-2001294 | TP for 37.716-31-11 to introduce DC_2-13-66_n48 | Nokia, Verizon |
| R4-2001295 | TP for 37.716-31-11 to introduce DC_2-13-66_n66 | Nokia, Verizon |
| R4-2001296 | TP for 37.716-31-11 to introduce DC_2-46-48_n5 | Nokia, Verizon |
| R4-2001297 | TP for 37.716-31-11 to introduce DC_2-46-48_n66 | Nokia, Verizon |
| R4-2001542 | TP for TR 37 716-31-11 to include DC_2-7-66_n38 | Ericsson, Rogers |
| R4-2001543 | TP for TR 37 716-31-11 to include DC_2-66-71_n38 | Ericsson, Rogers |
| R4-2001544 | TP for TR 37 716-31-11 to include DC_2-7-66_n71 | Ericsson, Rogers |
| R4-2001545 | TP for TR 37 716-31-11 to include DC_2-66-71_n66 | Ericsson, Rogers |
| R4-2001546 | TP for TR 37 716-31-11 to include DC_2-66-71_n78 | Ericsson, Rogers |
| R4-2001984 | TP for TR 37 716-31-11 to include DC_2A-48A-66A_n71A | Ericsson, US Cellular |
| R4-2001985 | TP for TR 37 716-31-11 to include DC_12A-48A-66A_n71A | Ericsson, US Cellular |
| R4-2001986 | TP for TR 37 716-31-11 to include DC_2A-12A-48A_n71A | Ericsson, US Cellular |
| R4-2001987 | TP for TR 37 716-31-11 to include DC_2A-12A-66A_n71A | Ericsson, US Cellular |
| R4-2001988 | TP for TR 37 716-31-11 to include DC_5A-48A-66A_n71A | Ericsson, US Cellular |
| R4-2001989 | TP for TR 37 716-31-11 to include DC_2A-5A-48A_n71A | Ericsson, US Cellular |
| R4-2001990 | TP for TR 37 716-31-11 to include DC_2A-5A-66A_n71A | Ericsson, US Cellular |
| R4-2001991 | TP for TR 37 716-31-11 to include DC_5A-12A-48A_n71A | Ericsson, US Cellular |
| R4-2001992 | TP for TR 37 716-31-11 to include DC_5A-12A-66A_n71A | Ericsson, US Cellular |
| R4-2001993 | TP for TR 37 716-31-11 to include DC_2A_5A-12A_n71A | Ericsson, US Cellular |
| R4-2001994 | TP for TR 37 716-31-11 to include DC_2A-48A-66A_n12A | Ericsson, US Cellular |
| R4-2001995 | TP for TR 37 716-31-11 to include DC_48A-66A-(n)12AA | Ericsson, US Cellular |
| R4-2001996 | TP for TR 37 716-31-11 to include DC_2A-48A-(n)12AA | Ericsson, US Cellular |
| R4-2001997 | TP for TR 37 716-31-11 to include DC_2A-66A-(n)12AA | Ericsson, US Cellular |
| R4-2002005 | draft Rel-16 CR to 38.101-3 to add CA_n7B UL for four band DC combinations | Ericsson, Telstra |
| R4-2002589 | TP to TR 37.716-31-11: Addition of DC_2A-5A_(n)12AA | Nokia, US Cellular |
| R4-2002590 | TP to TR 37.716-31-11: Addition of DC_2A-12A_(n)5AA | Nokia, US Cellular |
| R4-2002591 | TP to TR 37.716-31-11: Addition of DC_2A-48A_(n)5AA | Nokia, US Cellular |
| R4-2002592 | TP to TR 37.716-31-11: Addition of DC_2A-66A_(n)5AA | Nokia, US Cellular |
| R4-2002593 | TP to TR 37.716-31-11: Addition of DC_5A-48A_(n)12AA | Nokia, US Cellular |
| R4-2002594 | TP to TR 37.716-31-11: Addition of DC_5A-66A_(n)12AA | Nokia, US Cellular |
| R4-2002595 | TP to TR 37.716-31-11: Addition of DC_12A-48A_(n)5AA | Nokia, US Cellular |
| R4-2002596 | TP to TR 37.716-31-11: Addition of DC_12A-66A_(n)5AA | Nokia, US Cellular |
| R4-2002622 | TP for TR 37 716-31-11 to include DC_12A-48A-66A_n71A | Ericsson, US Cellular |
| R4-2002623 | TP for TR 37 716-31-11 to include DC_2A-12A-48A_n71A | Ericsson, US Cellular |
| R4-2002624 | TP for TR 37 716-31-11 to include DC_2A-12A-66A_n71A | Ericsson, US Cellular |
| R4-2002625 | TP for TR 37 716-31-11 to include DC_5A-12A-48A_n71A | Ericsson, US Cellular |
| R4-2002626 | TP for TR 37 716-31-11 to include DC_5A-12A-66A_n71A | Ericsson, US Cellular |
| R4-2002627 | TP for TR 37 716-31-11 to include DC_2A_5A-12A_n71A | Ericsson, US Cellular |
| R4-2002629 | draft Rel-16 CR to 38.101-3 to add CA_n7B UL for four band DC combinations | Ericsson, Telstra |
| 9.6.1 | Rapporteur Input (WID/TR/CR) [DC_R16_4BLTE_1BNR_5DL2UL-Core/Perf] | |
| R4-2001284 | Revised WID on Dual Connectivity (EN-DC) of 4 bands LTE inter-band CA (4DL/1UL) and 1 NR band (1DL/1UL) | Nokia, Nokia Shanghai Bell |
| R4-2001285 | CR to introduce new combinations of LTE 4band + NR 1band for TS 38.101-3 | Nokia, Nokia Shanghai Bell |
| R4-2001286 | draftTR 37.716-41-11 v0.7.0 | Nokia, Nokia Shanghai Bell |
| R4-2002608 | draftTR 37.716-41-11 v0.7.0 | Nokia, Nokia Shanghai Bell |
| 9.6.3 | EN-DC with FR2 band [DC_R16_4BLTE_1BNR_5DL2UL-Core] | |
| R4-2000877 | draft CR for correction DC of LTE 4bands + NR 1band (FR2) for TS 38.101-3 | KDDI Corporation |
| 9.7.1 | Rapporteur Input (WID/TR/CR) [DC_R16_xBLTE_2BNR_yDL2UL-Core/Per] | |
| R4-2001042 | TR 37.716-21-21 v0.9.0 update: LTE(xDL/1UL)+ NR(2DL/1UL) DC in rel-16 | LG Electronics France |
| R4-2001064 | Revised WID on LTE (xDL/UL x=1.2,3,4) with NR 2 bands (2DL/1UL) EN DC in rel-16 | LG Electronics France |
| R4-2001066 | Introducing CR on new EN-DC LTE(xDL/1UL)+ NR(2DL/1UL) DC in rel-16 | LG Electronics France |
| 9.7.2 | EN-DC including NR inter CA without FR2 band [DC_R16_xBLTE_2BNR_yDL2UL-Core] | |
| R4-2000102 | TP for TR 37.716-21-21: DC_66_n5-n48 | Verizon UK Ltd |
| R4-2000103 | TP for TR 37.716-21-21: DC_13_n48-n66 | Verizon UK Ltd |
| R4-2000105 | TP for TR 37.716-21-21: DC_13_n5-n48 | Verizon UK Ltd |
| R4-2000106 | TP for TR 37.716-21-21: DC_13-66_n5-n48 | Verizon UK Ltd |
| R4-2000182 | Draft CR: Adding EN-DC configurations to DC_3-20_n28-n78 | Nokia, Nokia Shanghai Bell, BT plc |
| R4-2000263 | TP for TR 37.716-21-21: DC_2A_n66A-n78A | Samsung, Bell mobility |
| R4-2000264 | TP for TR 37.716-21-21: DC_2A-7A_n66A-n78A and DC_2A-7A-7A_n66A-n78A | Samsung, Bell mobility |
| R4-2000265 | TP for TR 37.716-21-21: DC_2A-7A-66A_n66A-n78A and DC_2A-7A-7A-66A_n66A-n78A | Samsung, Bell mobility |
| R4-2000266 | TP for TR 37.716-21-21: DC_2A-66A_n66A-n78A | Samsung, Bell mobility |
| R4-2000267 | TP for TR 37.716-21-21: DC_7A_n66A-n78A | Samsung, Bell mobility |
| R4-2000268 | TP for TR 37.716-21-21: DC_7A-7A_n66A-n78A | Samsung, Bell mobility |
| R4-2000269 | TP for TR 37.716-21-21: DC_7A-66A_n66A-n78A and DC_7A-7A-66A_n66A-n78A | Samsung, Bell mobility |
| R4-2000270 | TP for TR 37.716-21-21: DC_66A_n66A-n78A | Samsung, Bell mobility |
| R4-2000480 | TP for TR37.716-21-21: DC_1A-3A-20A_n38A-n78A | ZTE Corporation |
| R4-2000481 | TP for TR37.716-21-21_ DC_1A-20A_n3A-n38A | ZTE Corporation |
| R4-2000482 | TP for TR37.716-21-21_ DC_1A-20A_n3A-n78A | ZTE Corporation |
| R4-2000483 | TP for TR37.716-21-21_ DC_1A-20A-38A_n3A-n78A | ZTE Corporation |
| R4-2000484 | TP for TR37.716-21-21: DC_3A-20A_n38A-n78A | ZTE Corporation |
| R4-2000485 | TP for TR37.716-21-21: DC_7A-20A_n3A-n78A | ZTE Corporation |
| R4-2000846 | TP for TR 37.716-21-21:DC_2_n7-n78 | Huawei, HiSilicon |
| R4-2000851 | TP for TR 37.716-21-21: UE requirements for DC_3-3-7-8_n1-n78, DC_3-7-7-8_n1-n78, DC_3-3-7-7-8_n1-n78 | CHTTL |
| R4-2000856 | TP for TR 37.716-21-21: UE requirements for DC_3-3-8_n1-n78, DC_7-7-8_n1-n78 | CHTTL |
| R4-2001092 | TP to TR 37.716.21-21: Addition of CA configuration for DC_1A_n8A-n78A | Huawei Technologies R&D UK |
| R4-2001128 | TP on summary of self-interference analysis for new EN-DC LTE(xDL/1UL)+ NR(2DL/1UL) DC in rel-16 | LG Electronics France |
| R4-2001130 | MSD results for new EN-DC LTE(xDL/1UL)+ NR(2DL/1UL) DC in rel-16 | LG Electronics France |
| R4-2001998 | TP for TR 37.716-21-21 to include DC_28_n7-n78 | Ericsson, Telstra |
| R4-2001999 | TP for TR 37.716-21-21 to include DC_3-28_n7-n78 | Ericsson, Telstra |
| R4-2002000 | TP for TR 37.716-21-21 to include DC_1-28_n7-n78 | Ericsson, Telstra |
| R4-2002001 | TP for TR 37.716-21-21 to include DC_1-3-28_n7-n78 | Ericsson, Telstra |
| R4-2002002 | draft CR adding configurations for 1_n7-n78, 3_n7-n78, 1-3_n7-n78, 3_n7-n78 | Ericsson, Telstra |
| R4-2002008 | TP for TR 37.716-21-21 to include DC_7A-28A_n3A-n78A, DC_7C-28A_n3A-n78A | Ericsson, Telstra |
| R4-2002011 | draft Rel-16 CR to 38.101-3 to add new configurations for 2_n41-n71, 66_n25-n41, 66_n41-n71, 2-66_n41-n71 to existing combinations | Ericsson, T-Mobile US |
| R4-2002013 | TP for TR 37.716-21-21 to include DC_2_n41-n66 | Ericsson, T-Mobile US |
| R4-2002014 | TP for TR 37.716-21-21 to include DC_2_n66-n71 | Ericsson, T-Mobile US |
| R4-2002016 | TP for TR 37.716-21-21 to include 66_n25-n71 | Ericsson, T-Mobile US |
| R4-2002017 | TP for TR 37.716-21-21 to include DC_2-46_n41-n66 | Ericsson, T-Mobile US |
| R4-2002018 | TP for TR 37.716-21-21 to include DC_2-66_n71-n261 | Ericsson, T-Mobile US |
| R4-2002649 | TP for TR 37.716-21-21: DC_2A-66A_n66A-n78A | Samsung, Bell mobility |
| R4-2002650 | TP for TR 37.716-21-21: DC_7A_n66A-n78A | Samsung, Bell mobility |
| R4-2002651 | TP for TR37.716-21-21_ DC_1A-20A_n3A-n38A | ZTE Corporation |
| R4-2002652 | TP for TR37.716-21-21_ DC_1A-20A-38A_n3A-n78A | ZTE Corporation |
| R4-2002653 | TP for TR 37.716-21-21:DC_2_n7-n78 | Huawei, HiSilicon |
| R4-2002654 | MSD results for new EN-DC LTE(xDL/1UL)+ NR(2DL/1UL) DC in rel-16 | LG Electronics France |
| R4-2002655 | TP for TR 37.716-21-21 to include DC_2-46_n41-n66 | Ericsson, T-Mobile US |
| R4-2002656 | TP for TR 37.716-21-21 to include DC_2-66_n71-n261 | Ericsson, T-Mobile US |
| 9.7.3 | EN-DC including NR inter CA with FR2 band [DC_R16_xBLTE_2BNR_yDL2UL-Core] | |
| R4-2000537 | TP for TR 37.716-21-21: DC_66A_n12A-n258A | Nokia, US Cellular |
| R4-2000538 | TP for TR 37.716-21-21: DC_66A_n12A-n260A | Nokia, US Cellular |
| R4-2000539 | TP for TR 37.716-21-21: DC_66A_n12A-n261A | Nokia, US Cellular |
| R4-2000762 | Draft CR for TS 38.101-3: Support of n77(2A) in DC_1-8_n77-n257 | SoftBank Corp. |
| R4-2000765 | Draft CR for TS 38.101-3: Support of n77(2A) in DC_1_n77-n257, 3_n77-n257 and 8_n77-n257 | SoftBank Corp. |
| R4-2000776 | TP for TR 37.716-21-21: EN-DC_11_n77-n257 | SoftBank Corp. |
| R4-2000777 | TP for TR 37.716-21-21: EN-DC_28_n77-n257 | SoftBank Corp. |
| R4-2000860 | TP for EN-DC of 1-3-21_n78-n257 for TR37.716-21-21 | NTT DOCOMO, INC. |
| R4-2000861 | TP for EN-DC of 1-19-42_n78-n257 for TR37.716-21-21 | NTT DOCOMO, INC. |
| R4-2000862 | TP for EN-DC of 1-21-42_n78-n257 for TR37.716-21-21 | NTT DOCOMO, INC. |
| R4-2000863 | TP for EN-DC of 19-21-42_n78-n257 for TR37.716-21-21 | NTT DOCOMO, INC. |
| R4-2000864 | TP for EN-DC of 1-3-21_n79-n257 for TR37.716-21-21 | NTT DOCOMO, INC. |
| R4-2000865 | TP for EN-DC of 1-19-42_n79-n257 for TR37.716-21-21 | NTT DOCOMO, INC. |
| R4-2000866 | TP for EN-DC of 1-21-42_n79-n257 for TR37.716-21-21 | NTT DOCOMO, INC. |
| R4-2000867 | TP for EN-DC of 19-21-42_n79-n257 for TR37.716-21-21 | NTT DOCOMO, INC. |
| R4-2000868 | TP for EN-DC of 1-3-21_n77-n257 for TR37.716-21-21 | NTT DOCOMO, INC. |
| R4-2000869 | TP for EN-DC of 1-19-42_n77-n257 for TR37.716-21-21 | NTT DOCOMO, INC. |
| R4-2000870 | TP for EN-DC of 1-21-42_n77-n257 for TR37.716-21-21 | NTT DOCOMO, INC. |
| R4-2000871 | TP for EN-DC of 19-21-42_n77-n257 for TR37.716-21-21 | NTT DOCOMO, INC. |
| R4-2000879 | draft CR for introduce DC of LTE 2bands + NR 2band for TS 38.101-3 | KDDI Corporation |
| R4-2000880 | draft CR for introduce DC of LTE 3bands + NR 2band for TS 38.101-3 | KDDI Corporation |
| R4-2000882 | draft CR for introduce DC of LTE 4bands + NR 2band for TS 38.101-3 | KDDI Corporation |
| R4-2000888 | CR to TS38.101-3 on band combination for Inter-band EN-DC | Samsung |
| R4-2001093 | draft CR for EN-DC inc NR CA FR1+FR2 w xDL_2ULfor TS 38.101-3 | NTT DOCOMO, INC. |
| R4-2001094 | TP for DC_1-19_n77-n257 for TR 37.716-21-21 | NTT DOCOMO, INC. |
| R4-2001095 | TP for DC_1-19_n78-n257 for TR 37.716-21-21 | NTT DOCOMO, INC. |
| R4-2001096 | TP for DC_1-19_n79-n257 for TR 37.716-21-21 | NTT DOCOMO, INC. |
| R4-2001097 | TP for DC_1-21_n77-n257 for TR 37.716-21-21 | NTT DOCOMO, INC. |
| R4-2001098 | TP for DC_1-21_n78-n257 for TR 37.716-21-21 | NTT DOCOMO, INC. |
| R4-2001099 | TP for DC_1-21_n79-n257 for TR 37.716-21-21 | NTT DOCOMO, INC. |
| R4-2001100 | TP for DC_1-3_n79-n257 for TR 37.716-21-21 | NTT DOCOMO, INC. |
| R4-2001101 | TP for DC_1-42_n77-n257 for TR 37.716-21-21 | NTT DOCOMO, INC. |
| R4-2001102 | TP for DC_1-42_n79-n257 for TR 37.716-21-21 | NTT DOCOMO, INC. |
| R4-2001103 | TP for DC_19-21_n77-n257 for TR 37.716-21-21 | NTT DOCOMO, INC. |
| R4-2001104 | TP for DC_19-21_n78-n257 for TR 37.716-21-21 | NTT DOCOMO, INC. |
| R4-2001105 | TP for DC_19-21_n79-n257 for TR 37.716-21-21 | NTT DOCOMO, INC. |
| R4-2001106 | TP for DC_19-42_n77-n257 for TR 37.716-21-21 | NTT DOCOMO, INC. |
| R4-2001107 | TP for DC_19-42_n78-n257 for TR 37.716-21-21 | NTT DOCOMO, INC. |
| R4-2001108 | TP for DC_19-42_n79-n257 for TR 37.716-21-21 | NTT DOCOMO, INC. |
| R4-2001109 | TP for DC_21-42_n77-n257 for TR 37.716-21-21 | NTT DOCOMO, INC. |
| R4-2001110 | TP for DC_21-42_n78-n257 for TR 37.716-21-21 | NTT DOCOMO, INC. |
| R4-2001111 | TP for DC_21-42_n79-n257 for TR 37.716-21-21 | NTT DOCOMO, INC. |
| R4-2001112 | TP for DC_3-19_n77-n257 for TR 37.716-21-21 | NTT DOCOMO, INC. |
| R4-2001113 | TP for DC_3-19_n78-n257 for TR 37.716-21-21 | NTT DOCOMO, INC. |
| R4-2001114 | TP for DC_3-19_n79-n257 for TR 37.716-21-21 | NTT DOCOMO, INC. |
| R4-2001115 | TP for DC_3-21_n77-n257 for TR 37.716-21-21 | NTT DOCOMO, INC. |
| R4-2001116 | TP for DC_3-21_n78-n257 for TR 37.716-21-21 | NTT DOCOMO, INC. |
| R4-2001117 | TP for DC_3-21_n79-n257 for TR 37.716-21-21 | NTT DOCOMO, INC. |
| R4-2001118 | TP for DC_3-42_n77-n257 for TR 37.716-21-21 | NTT DOCOMO, INC. |
| R4-2001119 | TP for DC_3-42_n78-n257 for TR 37.716-21-21 | NTT DOCOMO, INC. |
| R4-2001120 | TP for DC_3-42_n79-n257 for TR 37.716-21-21 | NTT DOCOMO, INC. |
| R4-2001121 | TP for DC_42_n77-n257 for TR 37.716-21-21 | NTT DOCOMO, INC. |
| R4-2001122 | TP for DC_42_n79-n257 for TR 37.716-21-21 | NTT DOCOMO, INC. |
| R4-2001981 | TP for TR 37.716-21-21 to include DC_2A_n12A-n258A | Ericsson, US Cellular |
| R4-2001982 | TP for TR 37.716-21-21 to include DC_2A_n12A-n260A | Ericsson, US Cellular |
| R4-2001983 | TP for TR 37.716-21-21 to include DC_2A_n12A-n261A | Ericsson, US Cellular |
| R4-2002015 | TP for TR 37.716-21-21 to include DC_2_n71-n261 | Ericsson, T-Mobile US |
| R4-2002657 | TP for TR 37.716-21-21: DC_66A_n12A-n258A | Nokia, US Cellular |
| R4-2002658 | TP for TR 37.716-21-21: DC_66A_n12A-n260A | Nokia, US Cellular |
| R4-2002659 | TP for TR 37.716-21-21: DC_66A_n12A-n261A | Nokia, US Cellular |
| R4-2002660 | TP for EN-DC of 1-21-42_n77-n257 for TR37.716-21-21 | NTT DOCOMO, INC. |
| R4-2002661 | TP for TR 37.716-21-21 to include DC_2A_n12A-n258A | Ericsson, US Cellular |
| R4-2002662 | TP for TR 37.716-21-21 to include DC_2A_n12A-n260A | Ericsson, US Cellular |
| R4-2002663 | TP for TR 37.716-21-21 to include DC_2A_n12A-n261A | Ericsson, US Cellular |
| R4-2002664 | TP for TR 37.716-21-21 to include DC_2_n71-n261 | Ericsson, T-Mobile US |
| 9.8.1 | Rapporteur Input (WID/TR/CR) [NR_SUL_combos_R16-Core/Per] | |
| R4-2001067 | Revised WID on Band combinations for SA NR Supplementary uplink (SUL), NSA NR SUL, NSA NR SUL with UL sharing from the UE perspective (ULSUP) | Huawei, HiSilicon |
| 9.8.2 | UE RF [NR_SUL_combos_R16-Core] | |
| R4-2001302 | TP for 37.716-21-21 to introduce DC_2-46_n41-n71 | Nokia, T-Mobile US |
| R4-2001303 | TP for 37.716-21-21 to introduce DC_2-46-66_n41-n71 | Nokia, T-Mobile US |
| R4-2001304 | TP for 37.716-21-21 to introduce DC_46-66_n25-n41 | Nokia, T-Mobile US |
| R4-2001305 | TP for 37.716-21-21 to introduce DC_46-66_n41-n71 | Nokia, T-Mobile US |
| R4-2002026 | UL Configuration for ULSUP TDM combinations | Skyworks Solutions Inc. |
| R4-2002071 | CR to 38.101-3 on EN-DC band combination with SUL for n41 | Google Inc. |
| R4-2002665 | CR to 38.101-3 on EN-DC band combination with SUL for n41 | Google Inc. |
| 9.9.1 | Rapporteur Input (WID/TR/CR) [NR_CA_R16_3BDL_1BUL-Core/Per] | |
| R4-2000624 | TR 38.716-03-01 v 0.2.0 | CATT |
| R4-2000625 | Introducing NR inter-band CA for 3DL Bands and 1UL band for 38.101-1 | CATT |
| R4-2000626 | Introducing NR inter-band CA for 3DL Bands and 1UL band for 38.101-3 | CATT |
| R4-2000627 | Revised WID: Rel-16 NR inter-band CA for 3 bands DL with 1 band UL | CATT |
| R4-2002921 | Introducing NR inter-band CA for 3DL Bands and 1UL band for 38.101-1 | CATT |
| 9.9.2 | UE RF [NR_CA_R16_3BDL_1BUL-Core] | |
| R4-2000144 | TP for TR38.716-03-01: Requirements for CA_n29A-n66A-n70A, CA_n29A-n66B-n70A, and CA_n29A-n66(2A)-n70A | Dish Network |
| R4-2000185 | TP to TR 38.716-03-01: CA_n25-n41-n71 | Nokia, Nokia Shanghai Bell, T-Mobile USA |
| R4-2000186 | TP to TR 38.716-03-01: CA_n41-n66-n71 | Nokia, Nokia Shanghai Bell, T-Mobile USA |
| R4-2000420 | CR for 38.101-1: Removal of inter-band CA redundancies | Sprint Corporation |
| R4-2000487 | CR to TS 38.101-1: Improvement on NR 3DL inter-band CA combination | ZTE Corporation |
| R4-2000760 | Draft CR for TS 38.101-1: Support of n77(2A) in CA_n3-n28-n77 | SoftBank Corp. |
| R4-2000847 | TP for TR 38.716-03-01:CA_n25-n66-n78 | Huawei, HiSilicon |
| R4-2000848 | TP for TR 38.716-03-01: CA_n7-n66-n78 | Huawei, HiSilicon |
| R4-2000849 | TP for TR 38.716-03-01: CA_n5-n66-n78 | Huawei, HiSilicon |
| R4-2000850 | TP for TR 38.716-03-01: CA_n7-n25-n66 | Huawei, HiSilicon |
| R4-2001063 | TP for TR 38.716-03-01: CA_n20A-n28A-n78A_BCS0 | Huawei, HiSilicon |
| R4-2001520 | TP for TR 38.716-03-01 to include CA_n1-n7-n28 | Ericsson, BT plc |
| R4-2001521 | TP for TR 38.716-03-01 to include CA_n1-n7-n78 | Ericsson, BT plc |
| R4-2002666 | TP for TR38.716-03-01: Requirements for CA_n29A-n66A-n70A, CA_n29A-n66B-n70A, and CA_n29A-n66(2A)-n70A | Dish Network |
| R4-2002667 | TP for TR 38.716-03-01: CA_n20A-n28A-n78A_BCS0 | Huawei, HiSilicon |
| R4-2002715 | CR to TS 38.101-1: Improvement on NR 3DL inter-band CA combination | ZTE Corporation |
| 9.10.1 | Rapporteur Input (WID/TR/CR) [NR_CA_R16_4BDL_1BUL-Core/Per] | |
| R4-2001501 | Revised WID 4 bands NR CA Rel-16 | Ericsson |
| R4-2001504 | TR 38.716-04-01 v0.2.0 Rel-16 NR Inter-band 4 bands CA | Ericsson |
| R4-2001508 | TP for TR 38.716-04-01 for updated scope from RAN #86 | Ericsson |
| R4-2001513 | CR introduction completed band combinations 38.716-04-01 -> 38.101-1 | Ericsson |
| R4-2001514 | CR introduction completed band combinations 38.716-04-01 -> 38.101-3 | Ericsson |
| R4-2002668 | Revised WID 4 bands NR CA Rel-16 | Ericsson |
| 9.10.2 | UE RF [NR_CA_R16_4BDL_1BUL-Core] | |
| R4-2000761 | Draft CR for TS 38.101-3: Support of n77(2A) in CA_n3-n28-n77-n257 | SoftBank Corp. |
| 9.11.1 | Rapporteur Input (WID/TR/CR) [NR_CADC_R16_3BDL_2BUL-Core/Per] | |
| R4-2000499 | CR to reflect the completed NR inter band CA DC combinations for 3 bands DL with 2 bands UL into Rel16 TS 38.101-1 | ZTE Corporation |
| R4-2000500 | CR to reflect the completed NR inter band CA DC combinations for 3 bands DL with 2 bands UL into Rel16 TS 38.101-3 | ZTE Corporation |
| R4-2000503 | Revised WID on Rel-16 NR Inter-band Carrier Aggregation/Dual Connectivity for 3 bands DL with 2 bands UL | ZTE Corporation |
| R4-2000804 | TR 38.716-03-02 v040 | ZTE Wistron Telecom AB |
| 9.11.2 | UE RF [NR_CADC_R16_3BDL_2BUL-Core] | |
| R4-2000145 | TP for TR38.716-03-02: UL CA Requirements for CA_n66A-n70A-n71A, CA_n66B-n70A-n71A, and CA_n66(2A)-n70A-n71A | Dish Network |
| R4-2000415 | CR for 38.101-3: Remove delta Tib and delta Rib for FR1+FR2 CA | Sprint Corporation |
| R4-2000475 | TP for TR38.716-03-02: updated the MSD value for CA_n3-n40A-n41A | ZTE Corporation |
| R4-2000476 | TP for TR38.716-03-02: updated the MSD value for CA_n40A-n41A-n79A | ZTE Corporation |
| R4-2000778 | TP for TR 38.716-03-02: CA_n3-n28-n77 | SoftBank Corp. |
| R4-2000779 | TP for TR 38.716-03-02: CA_n3-n28-n257 | SoftBank Corp. |
| R4-2001522 | TP for TR 38.716-03-02 to include CA_n1-n7-n28 | Ericsson, BT plc |
| R4-2001523 | TP for TR 38.716-03-02 to include CA_n1-n7-n78 | Ericsson, BT plc |
| R4-2002159 | CR for 38.101-3: delta Tib corrections | Sprint Corporation |
| R4-2002161 | CR for 38.101-1: delta Tib corrections | Sprint Corporation |
| R4-2002669 | TP for TR38.716-03-02: UL CA Requirements for CA_n66A-n70A-n71A, CA_n66B-n70A-n71A, and CA_n66(2A)-n70A-n71A | Dish Network |
| R4-2002670 | TP for TR 38.716-03-02: CA_n3-n28-n77 | SoftBank Corp. |
| R4-2002671 | TP for TR 38.716-03-02 to include CA_n1-n7-n28 | Ericsson, BT plc |
| R4-2002672 | CR for 38.101-1: delta Tib corrections | Sprint Corporation |
| R4-2002716 | CR for 38.101-3: Remove delta Tib and delta Rib for FR1+FR2 CA | Sprint Corporation |
| 9.12.1 | Rapporteur Input (WID/TR/CR) [DC_R16_LTE_NR_3DL3UL-Core/Per] | |
| R4-2000501 | CR to reflect the completed ENDC combinations for 3 bands DL with 3 bands UL into Rel16 TS 38.101-3 | ZTE Corporation |
| R4-2000504 | Revised WID: Dual Connectivity (EN-DC) with 3 bands DL and 3 bands UL | ZTE Corporation |
| 9.12.2 | UE RF [DC_R16_LTE_NR_3DL3UL-Core] | |
| R4-2000477 | TP for TR 37.716-33: DC_3A_n79A-n258 | ZTE Corporation |
| R4-2000558 | Correction to remedy missing implementation of approved CR0093r1 | ETSI MCC |
| R4-2001123 | draft CR for EN-DC inc NR CA FR1+FR2 w 3DL_3ULfor TS 38.101-3 | NTT DOCOMO, INC. |
| R4-2001124 | TP for DC_21_n77-n257 for TR 37.716-33 | NTT DOCOMO, INC. |
| R4-2001125 | TP for DC_21_n78-n257 for TR 37.716-33 | NTT DOCOMO, INC. |
| R4-2001126 | TP for DC_21_n79-n257 for TR 37.716-33 | NTT DOCOMO, INC. |
| R4-2002673 | draft CR for EN-DC inc NR CA FR1+FR2 w 3DL_3ULfor TS 38.101-3 | NTT DOCOMO, INC. |
| 9.13.1 | Rapporteur Input (WID/TR/CR) [DC_R16_xBLTE_2BNR_yDL3UL-Core/Per] | |
| R4-2000755 | draft TR skeleton TR 37.716-41-22 v0.0.1 | NTT DOCOMO INC. |
| R4-2002105 | Revised WID for Dual Connectivity (EN-DC) of LTE inter-band CA xDL/1UL bands (x=2,3,4) and NR FR1 1DL/1UL band and NR FR2 1DL/1UL band | NTT DOCOMO INC. |
| R4-2002106 | Updated TR 37.716-41-22 v0.1.0 | NTT DOCOMO INC. |
| R4-2002107 | CR for introduce new EN-DC of LTE 2,3,4 band + NR FR1 1UL/1DL band + NR FR2 1UL/1DL band for TS 38.101-3 | NTT DOCOMO INC. |
| 9.13.2 | UE RF [DC_R16_xBLTE_2BNR_yDL3UL-Core] | |
| R4-2001131 | TP for DC_1-3_n77-n257 for TR37.716-41-22 | NTT DOCOMO, INC. |
| R4-2001132 | TP for DC_1-21_n77-n257 for TR37.716-41-22 | NTT DOCOMO, INC. |
| R4-2001133 | TP for DC_1-42_n77-n257 for TR37.716-41-22 | NTT DOCOMO, INC. |
| R4-2001134 | TP for DC_3-19_n77-n257 for TR37.716-41-22 | NTT DOCOMO, INC. |
| R4-2001135 | TP for DC_3-21_n77-n257 for TR37.716-41-22 | NTT DOCOMO, INC. |
| R4-2001136 | TP for DC_3-42_n77-n257 for TR37.716-41-22 | NTT DOCOMO, INC. |
| R4-2001137 | TP for DC_19-21_n77-n257 for TR37.716-41-22 | NTT DOCOMO, INC. |
| R4-2001138 | TP for DC_19-42_n77-n257 for TR37.716-41-22 | NTT DOCOMO, INC. |
| R4-2001139 | TP for DC_21-42_n77-n257 for TR37.716-41-22 | NTT DOCOMO, INC. |
| R4-2001140 | TP for DC_1-3_n78-n257 for TR37.716-41-22 | NTT DOCOMO, INC. |
| R4-2001141 | TP for DC_1-21_n78-n257 for TR37.716-41-22 | NTT DOCOMO, INC. |
| R4-2001142 | TP for DC_1-42_n78-n257 for TR37.716-41-22 | NTT DOCOMO, INC. |
| R4-2001143 | TP for DC_3-19_n78-n257 for TR37.716-41-22 | NTT DOCOMO, INC. |
| R4-2001144 | TP for DC_3-21_n78-n257 for TR37.716-41-22 | NTT DOCOMO, INC. |
| R4-2001145 | TP for DC_3-42_n78-n257 for TR37.716-41-22 | NTT DOCOMO, INC. |
| R4-2001146 | TP for DC_19-21_n78-n257 for TR37.716-41-22 | NTT DOCOMO, INC. |
| R4-2001147 | TP for DC_19-42_n78-n257 for TR37.716-41-22 | NTT DOCOMO, INC. |
| R4-2001148 | TP for DC_21-42_n78-n257 for TR37.716-41-22 | NTT DOCOMO, INC. |
| R4-2001149 | TP for DC_1-3_n79-n257 for TR37.716-41-22 | NTT DOCOMO, INC. |
| R4-2001150 | TP for DC_1-21_n79-n257 for TR37.716-41-22 | NTT DOCOMO, INC. |
| R4-2001151 | TP for DC_1-42_n79-n257 for TR37.716-41-22 | NTT DOCOMO, INC. |
| R4-2001152 | TP for DC_3-19_n79-n257 for TR37.716-41-22 | NTT DOCOMO, INC. |
| R4-2001153 | TP for DC_3-21_n79-n257 for TR37.716-41-22 | NTT DOCOMO, INC. |
| R4-2001154 | TP for DC_3-42_n79-n257 for TR37.716-41-22 | NTT DOCOMO, INC. |
| R4-2001155 | TP for DC_19-21_n79-n257 for TR37.716-41-22 | NTT DOCOMO, INC. |
| R4-2001156 | TP for DC_19-42_n79-n257 for TR37.716-41-22 | NTT DOCOMO, INC. |
| R4-2001157 | TP for DC_21-42_n79-n257 for TR37.716-41-22 | NTT DOCOMO, INC. |
| R4-2001158 | TP for DC_1-19_n79-n257 for TR37.716-41-22 | NTT DOCOMO, INC. |
| R4-2001159 | TP for DC_1-3-21_n77-n257 for TR37.716-41-22 | NTT DOCOMO, INC. |
| R4-2001160 | TP for DC_19-21-42_n77-n257 for TR37.716-41-22 | NTT DOCOMO, INC. |
| R4-2001161 | TP for DC_1-21-42_n77-n257 for TR37.716-41-22 | NTT DOCOMO, INC. |
| R4-2001162 | TP for DC_1-3-21_n78-n257 for TR37.716-41-22 | NTT DOCOMO, INC. |
| R4-2001163 | TP for DC_19-21-42_n78-n257 for TR37.716-41-22 | NTT DOCOMO, INC. |
| R4-2001164 | TP for DC_1-21-42_n78-n257 for TR37.716-41-22 | NTT DOCOMO, INC. |
| R4-2001165 | TP for DC_1-3-21_n79-n257 for TR37.716-41-22 | NTT DOCOMO, INC. |
| R4-2001166 | TP for DC_19-21-42_n79-n257 for TR37.716-41-22 | NTT DOCOMO, INC. |
| R4-2001167 | TP for DC_1-21-42_n79-n257 for TR37.716-41-22 | NTT DOCOMO, INC. |
| R4-2001168 | TP for DC_1-19-42_n79-n257 for TR37.716-41-22 | NTT DOCOMO, INC. |
| 9.14 | 29dBm UE Power Class for B41 and n41 [LTE_NR_B41_Bn41_PC29dBm] | |
| R4-2002700 | Email discussion summary for RAN4#94e_#27_LTE_NR_B41_Bn41_PC29dBm | Moderator (Sprint) |
| R4-2002830 | WF on the clarification of A-MPR for different CG and EN-DC power classes | Sprint |
| R4-2002831 | WF on intra-band MPR/A-MPR curves | Sprint |
| R4-2002833 | WF on PC 1.5 behavior when P-Max is not present | KDDI |
| R4-2002834 | WF on EVM Impact of Reverse IMD3 on UL MIMO Modulation Order Capability | Qualcomm |
| R4-2002894 | Email discussion summary for RAN4#94e_#27_LTE_NR_B41_Bn41_PC29dBm | Moderator (Sprint) |
| R4-2002913 | Way Forward on A-MPR for PC1.5 intra-band EN-DC | Sprint |
| 9.14.2 | UE RF (36.101, 38.101-1, 38.101-3) [LTE_NR_B41_Bn41_PC29dBm] | |
| R4-2000007 | A-MPR Proposal for B41/n41 EN-DC | Apple Inc. |
| R4-2000111 | Discussion on TX diversity enabling 29 dBm power class | Qualcomm Incorporated |
| R4-2000112 | Draft CR to enable tx diversity for 29 dBm power class | Qualcomm Incorporated |
| R4-2000423 | CR for 38.101-3: Allocation aware MPR for intra-band EN-DC | Sprint Corporation |
| R4-2000424 | New SIB parameter to allow 29 dBm operation for LTE | Sprint Corporation |
| R4-2000425 | Applying the PC2 A-MPR requirements to PC1.5 | Sprint Corporation |
| R4-2000426 | 29 dBm HPUE Power Class logic | Sprint Corporation |
| R4-2000427 | CR for 36.101: Introduction of Power Class 1.5 | Sprint Corporation |
| R4-2000428 | CR for 36.307: Introduction of Power Class 1.5 | Sprint Corporation |
| R4-2000429 | CR for 38.101-1: Introduction of Power Class 1.5 | Sprint Corporation |
| R4-2000430 | CR for 38.101-3: Introduction of Power Class 1.5 | Sprint Corporation |
| R4-2000431 | CR for 38.307: Introduction of power class 1.5 | Sprint Corporation |
| R4-2000905 | Proposal on 29dBm P-Max issue for NR and LTE | CMCC |
| R4-2001239 | New A-MPR curves for 29dBm HPUE B41/n41 EN-DC | LG Electronics Finland |
| R4-2001547 | [29dBm] EVM Impact of Reverse IMD3 on UL MIMO Modulation Order Capability | Skyworks Solutions Inc. |
| R4-2002138 | Draft CR for 38.101-1: Introduction of Power Class 1.5 | Sprint Corporation |
| R4-2002140 | Draft CR for 38.101-3: Introduction of Power Class 1.5 | Sprint Corporation |
| R4-2002832 | CR for 38.101-3: Allocation aware MPR for intra-band EN-DC | Sprint Corporation |
| R4-2002914 | Applying the PC2 A-MPR requirements to PC1.5 | Sprint Corporation |
| 9.15 | Power Class 2 UE for EN-DC (1 LTE FDD band +1 NR TDD band) [ENDC_UE_PC2_FDD_TDD-Core] | |
| R4-2002701 | Email discussion summary for RAN4#94e_#28_ENDC_UE_PC2_FDD_TDD | Moderator (China Unicom) |
| R4-2002835 | WF on Power Class 2 high power UE for EN-DC | China Unicom |
| R4-2002895 | Email discussion summary for RAN4#94e_#28_ENDC_UE_PC2_FDD_TDD | Moderator (China Unicom) |
| 9.15.1 | General [ENDC_UE_PC2_FDD_TDD-Core] | |
| R4-2000316 | Discussion on power class 2 UE for EN-DC FDD-TDD | Samsung |
| R4-2000878 | Discussion on configurations for FDD-TDD EN-DC High Power UE | CHTTL |
| R4-2001037 | Consideration on SAR compliance schemes for PC2 FDD+TDD HPUE | China Unicom |
| 9.15.2 | UE RF requirement [ENDC_UE_PC2_FDD_TDD-Core] | |
| R4-2000447 | MSD analysis on high power UE for DC_3-n78 | Xiaomi |
| R4-2000908 | CR for adding power class 2 output power requirement for DC_3A_n41A | CMCC |
| R4-2001188 | MSD test results for Power Class 2 UE for EN-DC (1 LTE FDD band +1 NR TDD band) | LG Electronics France |
| R4-2001326 | Specification of EN-DC Power Class 2 for FDD-TDD band combinations | Ericsson |
| R4-2001327 | Introduction of EN-DC power class 2 for FDD-TDD band combinations | Ericsson |
| R4-2002097 | Power class and configured power for PC2 FDD-TDD EN-DC | Qualcomm Incorporated |
| R4-2002101 | Introduction of EN-DC power class 2 for FDD-TDD band combinations | Ericsson |
| 9.15.3 | Signaling [ENDC_UE_PC2_FDD_TDD-Core] | |
| R4-2000121 | on UE capability reporting for EN-DC (FDD+TDD) HPUE | vivo |
| R4-2000122 | Draft LS on UE capability for PC2 inter-band EN-DC (LTE FDD+NR TDD) | vivo |
| R4-2000968 | Discussion on HPUE for TDD+FDD | ZTE Corporation |
| 9.16 | Introduction of NR band n259 [NR_n259] | |
| R4-2001961 | TP to TR 38.887 on General issues | Ericsson |
| R4-2001968 | TR 38.88:7: Introduction of band n259 | Ericsson |
| R4-2002702 | Email discussion summary for RAN4#94e_#29_NR_n259 | Moderator (Ericsson) |
| R4-2002896 | Email discussion summary for RAN4#94e_#29_NR_n259 | Moderator (Ericsson) |
| R4-2002912 | TR 38.887: Introduction of band n259 | Ericsson |
| 9.16.1 | UE RF (38.101-2) [NR_n259-Core] | |
| R4-2000023 | Band n259 multi-band framework | Apple Inc. |
| R4-2000233 | EESS protection from n259 | NTT DOCOMO, INC. |
| R4-2000797 | n259 associated multi-band relaxation | MediaTek Beijing Inc. |
| R4-2001957 | Multiband relaxation for band n259 | Ericsson, Sony |
| R4-2001962 | TP to TR 38.887 on multiband relaxation | Ericsson |
| R4-2001964 | CR to 38.101-2 for Introduction of band n259 | Ericsson |
| R4-2002034 | Multi-band relaxation for n259 | Huawei, HiSilicon |
| R4-2002836 | CR to 38.101-2 for Introduction of band n259 | Ericsson |
| R4-2002837 | TP to TR 38.887 on General issues | Ericsson |
| 9.16.2 | BS RF (38.104) [NR_n259-Core] | |
| R4-2001192 | Additional unwanted emission requirements for the EESS protection from Band n259 | NTT DOCOMO, INC. |
| R4-2001960 | TP to TR 38.887 on BS RF requirements | Ericsson |
| R4-2001965 | CR to 38.141-2 for Introduction of band n259 | Ericsson |
| R4-2001966 | CR to 38.104 for Introduction of band n259 | Ericsson |
| R4-2002838 | TP to TR 38.887 on BS RF requirements | Ericsson |
| R4-2002839 | CR to 38.141-2 for Introduction of band n259 | Ericsson |
| R4-2002840 | CR to 38.104 for Introduction of band n259 | Ericsson |
| 9.16.3 | RRM (38.133) [NR_n259-Core] | |
| R4-2001956 | RRM requirements for introducy´tion of band n259 | Ericsson |
| R4-2001963 | TP to TR 38.887 on RRM | Ericsson |
| R4-2001967 | CR to 38.133 for Introduction of band n259 | Ericsson |
| R4-2002841 | TP to TR 38.887 on RRM | Ericsson |
| R4-2002842 | CR to 38.133 for Introduction of band n259 | Ericsson |
| 9.16.4 | Others [NR_n259-Core/Perf] | |
| R4-2001193 | BS conformance requirements for Band n259 | NTT DOCOMO, INC. |
| 9.17 | Adding 30MHz channel bandwidth for NR band n1 [NR_n1_BW] | |
| R4-2002703 | Email discussion summary for RAN4#94e_#30_NR_n1_BW | Moderator (Ericsson) |
| R4-2002845 | WF on UE RF requirements for adding 50 MHz channel BW to band n1 | Huawei |
| R4-2002897 | Email discussion summary for RAN4#94e_#30_NR_n1_BW | Moderator (Ericsson) |
| 9.17.1 | UE RF (38.101-1) [NR_n1_BW-Core] | |
| R4-2000825 | A-MPR simulation results for n1 30 MHz/40 MHz | Huawei, HiSilicon |
| R4-2001203 | CR to 38.101-1 Band n1 - wider CBW - Additional Channel BW | Ericsson, Huawei, China Unicom |
| R4-2002843 | CR to 38.101-1 Band n1 - wider CBW - Additional Channel BW | Ericsson, Huawei, China Unicom |
| 9.17.2 | BS RF (38.104) [NR_n1_BW-Core] | |
| R4-2001204 | CR to 38.104 Band n1 - wider CBW - Additional Channel BW | Ericsson, Huawei, China Unicom |
| R4-2002844 | CR to 38.104 Band n1 - wider CBW - Additional Channel BW | Ericsson, Huawei, China Unicom |
| 9.18 | Addition of wider channel bandwidth in NR band n28 [NR_n28_BW-Core] | |
| R4-2000165 | TR 38.888 v0.1.0 Adding wider channel bandwidths in NR band n28 | CBN |
| R4-2002704 | Email discussion summary for RAN4#94e_#31_NR_n28_BW | Moderator (CBN) |
| R4-2002898 | Email discussion summary for RAN4#94e_#31_NR_n28_BW | Moderator (CBN) |
| 9.18.1 | UE RF (38.101-1) [NR_n28_BW-Core] | |
| R4-2000090 | n28 AMPR for 30MHz BW | Qualcomm Incorporated |
| R4-2000493 | On UE REFSEN for 30MHz in band n28 | ZTE Corporation |
| R4-2000621 | UE co-existence reuiqrements for band n28 into 38.101-1 | CATT, CBN, ZTE, Huawei |
| R4-2001086 | CR for 38.101-1: introduce UE RF requirements for adding wider channel bandwidth in band n28 | Huawei, HiSilicon |
| R4-2001087 | TP on UE RF REFSENS for adding wider channel bandwidth in band n28 | Huawei, HiSilicon |
| R4-2001088 | TP on UE Tx RF requirements for adding wider channel bandwidth in band n28 | Huawei, HiSilicon, CBN |
| R4-2001089 | Updated 30MHz AMPR simulation results for NS_18 in band n28 | Huawei, HiSilicon |
| R4-2001226 | n28 supporting 30MHz REFSENS evaluation | MediaTek Inc. |
| R4-2002846 | TP on UE Tx RF requirements for adding wider channel bandwidth in band n28 | Huawei, HiSilicon, CBN |
| R4-2002847 | TP on UE RF REFSENS for adding wider channel bandwidth in band n28 | Huawei, HiSilicon |
| R4-2002849 | CR for 38.101-1: introduce UE RF requirements for adding wider channel bandwidth in band n28 | Huawei, HiSilicon |
| 9.18.2 | BS RF (38.104) [NR_n28_BW-Core] | |
| R4-2000623 | Introducing new channel bandwidth for band n28 | CATT, CBN, ZTE, Huawei |
| 9.18.4 | Others [NR_n28_BW-Core/Perf] | |
| R4-2000620 | Introducing new channel bandwidth for band n28 | CATT, CBN, ZTE, Huawei |
| R4-2000622 | UE co-existence reuiqrements for band n28 into 38.101-3 | CATT, CBN, ZTE, Huawei |
| R4-2001170 | Remove band 39 from protected band list of DC_1-n28 | CATT |
| R4-2002848 | Introducing new channel bandwidth for band n28 | CATT, CBN, ZTE, Huawei |
| 9.19 | Introduction of NR Band n26 [NR_n26] | |
| R4-2002705 | Email discussion summary for RAN4#94e_#32_NR_n26 | Moderator (Sprint) |
| R4-2002899 | Email discussion summary for RAN4#94e_#32_NR_n26 | Moderator (Sprint) |
| 9.19.1 | UE RF (38.101-1) [NR_n26] | |
| R4-2000008 | A-MPR Proposal for n26 | Apple Inc. |
| R4-2000092 | n26 AMPR | Qualcomm Incorporated |
| R4-2000432 | CR for 38.101-1: Introduction of n26 | Sprint Corporation |
| R4-2000527 | n26 A-MPR simulation results | Nokia |
| R4-2002145 | n26 PA Back-Off Measurements | Skyworks Solutions Inc. |
| R4-2002850 | n26 AMPR | Qualcomm Incorporated |
| 9.19.2 | BS RF (38.104) [NR_n26] | |
| R4-2000332 | Introduction of n26 | Nokia, Sprint |
| R4-2000333 | Introduction of n26 | Nokia, Sprint |
| R4-2000334 | Introduction of n26 | Nokia, Sprint |
| R4-2000335 | Introduction of n26 | Nokia, Sprint |
| R4-2000336 | Introduction of n26 | Nokia, Sprint |
| R4-2000337 | Introduction of n26 | Nokia, Sprint |
| R4-2000338 | Introduction of n26 | Nokia, Sprint |
| R4-2000339 | Introduction of n26 | Nokia, Sprint |
| R4-2000340 | Introduction of n26 | Nokia, Sprint |
| R4-2000341 | Introduction of n26 | Nokia, Sprint |
| 9.19.3 | RRM (38.133) [NR_n26] | |
| R4-2000506 | n26 introduction to 38.133 | Dish Network |
| 9.20 | Adding 25MHz and 50MHz channel bandwidth in NR band n1 [NR_n1_BW2] | |
| R4-2000813 | Draft CR 38.104 adding Band n1 50MHz channel bandwidth | China Unicom |
| 9.20.1 | UE RF (38.101-1) [NR_n1_BW2-Core] | |
| R4-2000108 | n1 AMPR for 50MHz Channel BW | Qualcomm Incorporated |
| R4-2000494 | On UE REFSEN for 50MHz of band n1 | ZTE Corporation |
| R4-2000826 | A-MPR simulation results for n1 25MHz | Huawei, HiSilicon |
| R4-2000827 | UE REFSENS for 50 MHz | Huawei, HiSilicon, China Unicom |
| 9.21 | Addition of asymmetric channel bandwidth for NR band n66 [NR_n66_BW] | |
| R4-2002706 | Email discussion summary for RAN4#94e_#33_NR_n66_BW | Moderator (Huawei) |
| R4-2002900 | Email discussion summary for RAN4#94e_#33_NR_n66_BW | Moderator (Huawei) |
| 9.21.1 | UE RF (38.101-1) [NR_n66_BW] | |
| R4-2000689 | Way forward on the n66 asymmetric channel bandwidth | Verizon UK Ltd |
| R4-2000828 | Further discussion on the support of asymmetric channel bandwidth | Huawei, HiSilicon |
| R4-2000829 | CR for TS 38.101: adding wider channel bandwidths for n66 | Huawei, HiSilicon |
| R4-2001953 | LS to RAN2 on addition of asymmetric channel bandwidth for band n66 | Huawei |
| R4-2002851 | CR for TS 38.101: adding wider channel bandwidths for n66 | Huawei, HiSilicon |
| R4-2002852 | LS to RAN2 on addition of asymmetric channel bandwidth for band n66 | RAN4 |
| 9.21.2 | BS RF (38.104) [NR_n66_BW] | |
| R4-2000830 | CR for TS 38.104: adding wider channel bandwidths for n66 | Huawei, HiSilicon |
| 9.22 | Adding wider channel bandwidth to NR band n38 [NR_n38_BW2] | |
| R4-2002707 | Email discussion summary for RAN4#94e_#34_NR_n38_BW2 | Moderator (Ericsson) |
| R4-2002901 | Email discussion summary for RAN4#94e_#34_NR_n38_BW2 | Moderator (Ericsson) |
| 9.22.1 | UE RF (38.101-1) [NR_n38_BW2] | |
| R4-2001208 | CR to 38.101-1 Band n38 - wider CBW - Additional Channel BW | Ericsson |
| R4-2002853 | CR to 38.101-1 Band n38 - wider CBW - Additional Channel BW | Ericsson |
| 9.22.2 | BS RF (38.104) [NR_n38_BW2] | |
| R4-2001209 | CR to 38.104 Band n38 - wider CBW - Additional Channel BW | Ericsson |
| 9.23 | LTE/NR spectrum sharing in band 48/n48 frequency range [NR_n48_LTE_48_coex-Core] | |
| R4-2002708 | Email discussion summary for RAN4#94e_#35_NR_n48_LTE_48_coex | Moderator (Apple) |
| R4-2002854 | WF on LTE/NR spectrum sharing in band 48/n48 | Apple |
| R4-2002902 | Email discussion summary for RAN4#94e_#35_NR_n48_LTE_48_coex | Moderator (Apple) |
| 9.23.1 | General (such as work plan, AH minutes) [NR_n48_LTE_48_coex-Core] | |
| R4-2000085 | Work plan for LTE/NR spectrum sharing in band 48/n48 frequency range | Apple Inc. |
| 9.23.2 | Channel raster, sync raster, and UL shift [NR_n48_LTE_48_coex-Core] | |
| R4-2000086 | LTE/NR spectrum sharing in band 48/n48 frequency range | Apple Inc. |
| R4-2000087 | Introduction of LTE/NR spectrum sharing in band 48/n48 frequency range | Apple Inc. |
| R4-2000095 | Introduction of LTE/NR spectrum sharing in band 48/n48 frequency range | Apple Inc. |
| R4-2000273 | DSS in LTE/NR band 48/n48 | Samsung |
| R4-2001043 | Views on band 48/n48 spectrum sharing | Nokia, Nokia Shanghai Bell |
| R4-2001386 | LTE/NR spectrum sharing in band 48/n48 | Ericsson |
| R4-2002048 | Views on dynamic spectrum sharing between LTE band 48 and NR band n48 | Google Inc. |
| R4-2002068 | CR to TS 38.104 on n48 dynamic spectrum sharing | Google Inc. |
| 9.24 | Adding 40 MHz channel bandwidth (15, 30 and 60kHz SCS) in NR band n3 [NR_n3_BW] | |
| R4-2002709 | Email discussion summary for RAN4#94e_#36_NR_n3_BW | Moderator (Ericsson) |
| R4-2002855 | WF on UE RF requirements for adding channel BW to band n3 | Ericsson |
| R4-2002903 | Email discussion summary for RAN4#94e_#36_NR_n3_BW | Moderator (Ericsson) |
| 9.24.1 | UE RF (38.101-1) [NR_n3_BW] | |
| R4-2000088 | n3 REFSENS | Qualcomm Incorporated |
| R4-2001205 | Band n3 - 40 MHz CBW – UE RF requirements | Ericsson |
| R4-2001206 | CR to 38.101-1 Band n3 - wider CBW - Additional Channel BW | Ericsson |
| 9.24.2 | BS RF (38.104) [NR_n3_BW] | |
| R4-2001207 | CR to 38.104 Band n3 - wider CBW - Additional Channel BW | Ericsson |
| 9.24.4 | Others [NR_n3_BW] | |
| R4-2002856 | WF on UE RF requirements for adding channel BW to band n65 | Ericsson |
| R4-2002904 | Email discussion summary for RAN4#94e_#37_NR_n65_BW | Moderator (Ericsson) |
| 9.25 | Adding 50 MHz channel bandwidth (15, 30 and 60kHz SCS) in NR band n65 [NR_n65_BW] | |
| R4-2002710 | Email discussion summary for RAN4#94e_#37_NR_n65_BW | Moderator (Ericsson) |
| 9.25.1 | UE RF (38.101-1) [NR_n65_BW] | |
| R4-2000089 | n65 50MHz AMPR | Qualcomm Incorporated |
| R4-2001210 | Band n65 - Adding Channel BW - UE RF REFSENS | Ericsson |
| R4-2001211 | Band n65 - Adding Channel BW - UE RF A-MPR | Ericsson |
| 9.26 | Introduction of NR Band n53 [NR_n53] | |
| R4-2000325 | Introduction of LTE re-farming band n53 to NR specification | Samsung Electronics Co., Ltd |
| R4-2002711 | Email discussion summary for RAN4#94e_#38_NR_n53 | Moderator (Globalstar) |
| R4-2002905 | Email discussion summary for RAN4#94e_#38_NR_n53 | Moderator (Globalstar) |
| 9.26.1 | UE RF (38.101-1) [NR_n53] | |
| R4-2000094 | n53 RF Requirements | Qualcomm Incorporated |
| R4-2000519 | Introduction of n53 into TS 38.101-1 | Nokia, Globalstar |
| R4-2002857 | Introduction of n53 into TS 38.101-1 | Nokia, Globalstar |
| 9.26.2 | BS RF (38.104) [NR_n53] | |
| R4-2000342 | Introduction of n53 | Nokia, Globalstar |
| R4-2000343 | Introduction of n53 | Nokia, Globalstar |
| R4-2000344 | Introduction of n53 | Nokia, Globalstar |
| R4-2000345 | Introduction of n53 | Nokia, Globalstar |
| R4-2000346 | Introduction of n53 | Nokia, Globalstar |
| R4-2000347 | Introduction of n53 | Nokia, Globalstar |
| R4-2000348 | Introduction of n53 | Nokia, Globalstar |
| R4-2000349 | Introduction of n53 | Nokia, Globalstar |
| R4-2000350 | Introduction of n53 | Nokia, Globalstar |
| R4-2000351 | Introduction of n53 | Nokia, Globalstar |
| R4-2002858 | Introduction of n53 | Nokia, Globalstar |
| R4-2002859 | Introduction of n53 | Nokia, Globalstar |
| R4-2002860 | Introduction of n53 | Nokia, Globalstar |
| 9.26.3 | RRM (38.133) [NR_n53] | |
| R4-2001347 | Introduction of n53 into 38.133 | Nokia, Nokia Shanghai Bell, Globalstar |
| 9.27 | Closed Rel-16 NR spectrum related WIs [WI code] | |
| R4-2000110 | Correction n91 and n93 UL channel BW | Qualcomm Incorporated |
| R4-2002712 | Email discussion summary for RAN4#94e_#39_NR_R16_Closed_WI | Moderator (Dish Network) |
| R4-2002906 | Email discussion summary for RAN4#94e_#39_NR_R16_Closed_WI | Moderator (Dish Network) |
| 9.27.1 | UE RF [WI code] | |
| R4-2000123 | CR on SAR solution for TDD&TDD EN-DC PC2 UE | vivo |
| R4-2000146 | Corrections to n65 | Dish Network |
| R4-2000412 | n41 and n90 network compatibility | Sprint Corporation |
| R4-2000419 | CR for 38.101-1: Missing 70 MHz for NS_01 | Sprint Corporation |
| R4-2000852 | Maintenance on the UE BW for n92 and n94 | Huawei, HiSilicon |
| R4-2001038 | Maintenance on the Rx-Tx separation terms | Huawei, HiSilicon |
| R4-2001075 | CR for 38.101-1 to correct CA_n8A-n75A REFSENS | Huawei, HiSilicon |
| R4-2002116 | CR for 38.101-1: Mandatory support for n41 by UEs that support n90 | Sprint Corporation |
| R4-2002139 | Correction to CA bandwidth class B | Qualcomm Incorporated |
| R4-2002861 | CR on SAR solution for TDD&TDD EN-DC PC2 UE | vivo |
| R4-2002863 | Maintenance on the UE BW for n92 and n94 | Huawei, HiSilicon |
| 9.27.2 | BS RF [WI code] | |
| R4-2001039 | Maintenance on the BS BW for n92 and n94 | Huawei, HiSilicon |
| 9.27.3 | RRM [WI code] | |
| R4-2000814 | introduce n18 into TS38.133 | KDDI Corporation |
| R4-2002862 | introduce n18 into TS38.133 | KDDI Corporation |
| 10.2.1 | General [FS_NR_MIMO_OTA_test] | |
| R4-2000894 | TR38.827 v1.1.0 NR MIMO OTA | CAICT |
| R4-2000897 | TP to TR 38.827 v1.1.0 on general part | CAICT |
| R4-2002388 | Email discussion summary for RAN4#94e_#97_FS_NR_MIMO_OTA_test | Moderator (CAICT) |
| R4-2002471 | WF on finalizing FR2 MIMO OTA | CAICT, Spirent |
| R4-2002472 | TP to TR 38.827 v1.1.0 on general part | CAICT |
| R4-2002481 | TP to TR38.827 on spatial sampling points for FR1 spatial correlation validation | Keysight |
| R4-2002482 | TR38.827 v1.2.0 NR MIMO OTA | CAICT |
| R4-2002526 | Email discussion summary for RAN4#94e_#97_FS_NR_MIMO_OTA_test | Moderator (CAICT) |
| 10.2.2 | Performance metrics [FS_NR_MIMO_OTA_test] | |
| R4-2000272 | Proposal on MIMO OTA performance metrics for FR2 | Samsung |
| R4-2000895 | TP to TR 38.827 v1.1.0 on FR2 MIMO OTA performance metrics | CAICT |
| 10.2.3.1 | FR1 test methodologies [FS_NR_MIMO_OTA_test] | |
| R4-2002156 | Reference Spatial Correlation Curves for Different NR FR1 MIMO OTA Test Frequencies | Keysight Technologies UK Ltd |
| 10.2.3.2 | FR2 test methodologies [FS_NR_MIMO_OTA_test] | |
| R4-2000080 | Dynamic geometry-based MIMO OTA Testing | Qualcomm Incorporated |
| R4-2000505 | Study feasible SNR ranges for NR FR2 MIMO OTA in 3D MPAC | Qualcomm Incorporated |
| R4-2000896 | TP to TR 38.827 v1.1.0 on FR2 preliminary MU assessment | CAICT |
| R4-2002069 | DoT selection for FR2 channel model | Spirent Communications |
| R4-2002070 | TP for DoT selection for FR2 channel model | Spirent Communications |
| R4-2002073 | System Design and Probe layout for FR2 MPAC MIMO OTA | Spirent Communications |
| R4-2002074 | TP for System Design and Probe layout for FR2 MPAC MIMO OTA | Spirent Communications |
| R4-2002100 | Verification of FR2 channel models in MPAC system | Spirent Communications |
| R4-2002102 | TP for Verification of FR2 channel models in MPAC system | Spirent Communications |
| R4-2002117 | Discussion on test system implementation for FR2 MIMO OTA | ROHDE & SCHWARZ |
| R4-2002151 | TP to TR38.827: FR2 MIMO OTA Calibration and Test Procedures | Keysight Technologies UK Ltd |
| R4-2002152 | TP to 38.827 to introduce EUT orientations for FR2 | Keysight Technologies UK Ltd |
| R4-2002153 | Sample SNR ranges in FR2 OTA setup | Keysight Technologies UK Ltd |
| R4-2002154 | PSP Correlation between two CE Vendors | Keysight Technologies UK Ltd, Spirent Communications |
| R4-2002155 | System Implementation of FR2 3D MPAC Systems | Keysight Technologies UK Ltd |
| R4-2002157 | Joint Power-Angle-Delay profiles for FR2 NR MIMO OTA channel models validation and PSP evaluation | Keysight Technologies UK Ltd |
| R4-2002364 | DoT selection for FR2 channel model | Spirent Communications |
| R4-2002365 | TP for Verification of FR2 channel models in MPAC systemTP for Verification of FR2 channel models in MPAC system | Spirent Communications |
| R4-2002473 | TP to TR 38.827 v1.1.0 on FR2 preliminary MU assessment | CAICT |
| R4-2002474 | TP for DoT selection for FR2 channel model | Spirent Communications |
| R4-2002475 | TP for Verification of FR2 channel models in MPAC systemTP for Verification of FR2 channel models in MPAC system | Spirent Communications |
| R4-2002476 | TP to TR38.827: FR2 MIMO OTA Calibration and Test Procedures | Keysight Technologies UK Ltd |
| R4-2002477 | PSP Correlation between two CE Vendors | Keysight Technologies UK Ltd, Spirent Communications |
| R4-2002478 | System Implementation of FR2 3D MPAC Systems | Keysight Technologies UK Ltd |
| R4-2002479 | Discussion on test system implementation for FR2 MIMO OTA | ROHDE |
| 10.2.4 | Channel Models [FS_NR_MIMO_OTA_test] | |
| R4-2000798 | Initial phase of MIMO OTA channel model | MediaTek Beijing Inc. |
| R4-2002149 | Clarification of Beam Forming Weights | Keysight Technologies UK Ltd |
| R4-2002150 | Initial phase definition of channel models | Keysight Technologies UK Ltd |
| R4-2002480 | Clarification of Beam Forming Weights | Keysight Technologies UK Ltd |
| R4-2002533 | Initial phase definition of channel models | Keysight Technologies UK Ltd |
| 10.3 | Study on 7 - 24GHz frequency range [FS_7to24GHz_NR] | |
| R4-2002713 | Email discussion summary for RAN4#94e_#40_FS_7to24GHz_NR | Moderator (Huawei) |
| R4-2002907 | Email discussion summary for RAN4#94e_#40_FS_7to24GHz_NR | Moderator (Huawei) |
| 10.3.1 | General [FS_7to24GHz_NR] | |
| R4-2001837 | TP to TR 38.820: cleanup | Huawei |
| R4-2001838 | TR 38.820, v2.0.0: implementation of TPs from RAN4#94-e | Huawei |
| R4-2002865 | TP to TR 38.820: cleanup | Huawei |
| R4-2002866 | TR 38.820, v2.0.0 | Huawei |
| 10.3.2 | Regulatory survey [FS_7to24GHz_NR] | |
| R4-2001834 | TP to TR 38.820: summary on the frequency bands of interest within 7-24 GHz range | Huawei |
| R4-2001835 | WRC-19 conclusions on IMT in 7 – 24 GHz range | Huawei |
| R4-2001836 | TP to TR 38.820: WRC-19 conclusions | Huawei |
| R4-2002867 | TP to TR 38.820: summary on the frequency bands of interest within 7-24 GHz range | Huawei |
| R4-2002868 | TP to TR 38.820: WRC-19 conclusions | Huawei |
| 10.3.5 | Deployment scenarios [FS_7to24GHz_NR] | |
| R4-2001017 | TP to TR 38.820: Addition of technical background for BS classes in subclause 7.3 | Ericsson |
| R4-2002869 | TP to TR 38.820: Addition of technical background for BS classes in subclause 7.3 | Ericsson |
| 10.3.6 | RF technology aspects [FS_7to24GHz_NR] | |
| R4-2001018 | TP to TR 38.820: Phase noise trends and example parameterized phase noise model in subclause 5.5.3 and Annex B | Ericsson |
| R4-2002870 | TP to TR 38.820: Phase noise trends and example parameterized phase noise model in subclause 5.5.3 and Annex B | Ericsson |
| 10.3.8.1 | BS types, BS requirement sets [FS_7to24GHz_NR] | |
| R4-2000673 | TP to TR 38.820: BS classes for 7-24 GHz frequency range | Nokia, Nokia Shanghai Bell |
| R4-2000686 | TP to TR 38.820: BS classes for 7-24 GHz frequency range | Nokia, Nokia Shanghai Bell |
| 10.3.8.4 | RX requirements [FS_7to24GHz_NR] | |
| R4-2000674 | TP to TR 38.820: Update of BS receiver requirements for 7-24 GHz frequency range | Nokia, Nokia Shanghai Bell |
| R4-2000687 | TP to TR 38.820: Update of BS receiver requirements for 7-24 GHz frequency range | Nokia, Nokia Shanghai Bell |
| R4-2001016 | TP to TR 38.820: Addition of technical background for co-location OOB receiver blocking in subclause 7.4 | Ericsson |
| R4-2002871 | TP to TR 38.820: Update of BS receiver requirements for 7-24 GHz frequency range | Nokia, Nokia Shanghai Bell |
| R4-2002872 | TP to TR 38.820: Addition of technical background for co-location OOB receiver blocking in subclause 7.4 | Ericsson |
| 12 | Liaison and output to other groups | |
| R4-2000781 | On secondary DRX group for FR1+FR2 CA | Apple |
| R4-2000782 | LS on secondary DRX group for FR1+FR2 CA | Apple |
| R4-2001753 | Discussions on RRM impact due to secondary DRX group | Ericsson |
| R4-2001755 | Draft Reply LS on secondary DRX group | Ericsson |
| 13.1 | Simplification of band combinations in RAN4 specifications | |
| R4-2001068 | Discussion on improvement of request, SR and BC basket WID index table | Huawei, HiSilicon |
| R4-2002108 | Further discussion on simplification of EN-DC configuration including FR2 | NTT DOCOMO INC. |
| 13.2 | R17 new proposals | |
| R4-2000009 | Views on the NR FR1 TRP/TRS requirement specification | Apple Inc. |
| R4-2000753 | New SID on high-power UE operation for fixed-wireless/vehicle-mounted use cases in Band 12 and in Band 5 | US Cellular Corporation |
| 13.2.1 | Basket WI approach for adding existing channel bandwidth on existing NR bands | |
| R4-2001213 | New Basket WI adding new CBW in existing NR bands - status | Ericsson |
| 13.2.2 | Proposals on adding “brand new” channel bandwidth | |
| R4-2000025 | Solutions for unusual Spectrum allocations for NR bands | Apple |
| R4-2000072 | Discussion for new WI on introduction of brand new channel bandwidths for NR | Huawei, HiSilicon |
| R4-2000073 | New WID proposal: introduction of brand new channel bandwidths for NR | Huawei, HiSilicon |
| R4-2000433 | Channel BWs discussion | Sprint Corporation |
| R4-2000434 | Channel BWs motivation | Sprint Corporation |
| R4-2000435 | New SID: Efficient utilization of licensed spectrum that is not aligned with existing NR channel bandwidths | Sprint Corporation |
| R4-2000651 | Discussion on solutions to handle brand new channel bandwidth | CMCC |
| R4-2001219 | On adding brand new channel bandwidth for existing band | MediaTek Inc |
| 13.2.3 | Basket WIs for LTE CA, EN-DC, NR CA and NR DC | |
| R4-2000274 | Proposal on new Rel-17 Basket: NR inter-band Carrier Aggregation and Dual connectivity for DL 4 bands and 2UL bands | Samsung |
| R4-2000496 | New WID: EN-DC of x bands (x=1,2,3) LTE inter-band CA (xDL/1UL) and 3 bands NR inter-band CA (3DL/1UL) | ZTE Corporation |
| R4-2001090 | New WI Rel-17 NR inter-band CA for 5 bands DL with x bands UL (x=1, 2) | Huawei, HiSilicon |
| R4-2001091 | Rel-17 New WID on SA NR SUL, NSA NR SUL, NSA NR SUL with UL sharing from the UE perspective (ULSUP) | Huawei, HiSilicon |
| 13.2.4 | Others | |
| R4-2000024 | FR2 RF enhancements for Rel-17 | Apple Inc. |
| R4-2000074 | New WID proposal: supporting overlapping CA for LTE | Huawei, HiSilicon |
| R4-2000075 | New WID proposal: Introduction of new FR2 FWA UE power class | Huawei, HiSilicon |
| R4-2000129 | Addition of operating bands (Downlink-Only) for LTE-based 5G Terrestrial Broadcast | ABS |
| R4-2000130 | New WI Proposal: LTE / NR Spectrum sharing in Band 40/n40 for LTE-NR Coexistence | Reliance Jio |
| R4-2000468 | Motivation to introduce new R17 WI on further RRM enhancement | MediaTek inc. |
| R4-2000587 | Motivation on further enhancement for NR RRM requirement in Rel-17 | CATT |
| R4-2000588 | New WID on further enhancement for NR RRM requirement in Rel-17 | CATT |
| R4-2000629 | Motivation on basket WI on V2X band combination | CATT |
| R4-2000630 | New basket WID: V2X band combination for supporting co-current operation between Uu frequency bands and V2X bands | CATT |
| R4-2000757 | New WID on Introduction of new FR2 FWA UE with maximum TRP of 23dBm | SoftBank Corp. |
| R4-2000758 | Motivation for Introduction of new FR2 FWA NR UE with maximum TRP of 23dBm | SoftBank Corp., Rakuten Mobile, KDDI, NTT DOCOMO |
| R4-2000788 | Motivation on Rel-17 further RRM enhancements | Apple |
| R4-2000883 | Consideration on NR SISO OTA WI | vivo |
| R4-2000884 | Motivation for NR FR1 UE TRP and TRS | vivo, CMCC, CAICT, Rohde & Schwarz |
| R4-2000885 | New WID: NR FR1 UE SA and EN-DC TRP and TRS | vivo, CMCC, CAICT, Rohde & Schwarz |
| R4-2000903 | New WID on air-to-ground network for NR | CMCC |
| R4-2000904 | Motivation for new WI on air-to-ground network for NR | CMCC |
| R4-2000957 | Motivation to introduce new R17 SI_WI on measurement gap enhancements | Intel Corporation, Apple |
| R4-2000971 | New proposed WID on Introduction of standalone NB-IoT into AAS spec | ZTE Corporation |
| R4-2001212 | New SID - 6GHz range investigation | Ericsson |
| R4-2001235 | New SID on NR FR1 and EN-DC FR1 UE TRP and TRS | OPPO |
| R4-2001236 | Motivation of NR FR1 TRP TRS new study item | OPPO |
| R4-2001801 | New WID: NR FR1 UE SA and EN-DC TRP and TRS | vivo, CMCC, CAICT, Rohde & Schwarz |
| 13.3 | Others | |
| R4-2000815 | New WID on introduction of n13 | Huawei, HiSilicon, Bell |
| 14 | Any other business | |
| R4-2000421 | CR for 36.101: Missing Pcmax tolerance for 23-33 dBm in Table 6.2.5A-2 and Table 6.2.5B-1 | Sprint Corporation |
| R4-2000422 | Mirror CR for 36.101: Missing Pcmax tolerance for 23-33 dBm in Table 6.2.5A-2 and Table 6.2.5B-1 | Sprint Corporation |
| R4-2001860 | Managing RAN4 work load | Ericsson, Nokia, Nokia Shanghai Bell, ZTE, Mediatek, Qualcomm, Verizon, AT&T, T-Mobile, Softbank, KDDI, NTT DoCoMo, Rohde & Schwarz, US Cellular |
| R4-2002110 | Clarification on Rx image assumption for intra-band non-contiguous NR CA/EN-DC | NTT DOCOMO INC. |
| R4-2002864 | CR for 36.101: Missing Pcmax tolerance for 23-33 dBm in Table 6.2.5A-2 and Table 6.2.5B-1 | Sprint Corporation |
| 15 | Close of the E-meeting | |
| R4-2002350 | TR 36.716-02-01-030 Rel-16 2 Bands DL and 1 Band UL CA | Qualcomm Incorporated |
| R4-2002351 | TR 36.716-03-02 v0.10.0 LTE-A inter-band CA for x bands (x=3,4,5) DL with 2 bands UL in Rel-16 | LG Electronics France |